← previous blocknext block →recent activity
Analyzing
Block #87,333,079
24 transactions · 20 stateful · 2026-07-12 19:34:37 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,333,079 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w17w08w111w213w014w116w217w121w022w123w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xacaba0ad…e266
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe73ab2bc…7cd9
0x34b655…2a6f
6 touches
3 conflicts
0x7b6d2deb…dde0
0x34b655…2a6f
6 touches
3 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x3347cbe5…846c
0x34b655…2a6f
4 touches
1 conflict
0x67db761a…4fa1
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
3 conflicts on slot 0xacaba0ade4…85e266
Audit this contract →
← previous block·next block →recent activity