← previous blocknext block →recent activity
Analyzing
Block #87,326,573
16 transactions · 16 stateful · 2026-07-12 18:51:07 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,326,573 · 16 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
1w02w13w27w08w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4b8c5b1…836b
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xc30eb194…6167
0x34b655…2a6f
6 touches
3 conflicts
0x342f88f5…2a06
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x17e5fbad…53ec
0x34b655…2a6f
4 touches
1 conflict
0x3312fcbd…c934
0x34b655…2a6f
4 touches
1 conflict
0x65e6e603…cb44
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 0xb4b8c5b109…eb836b
Audit this contract →
← previous block·next block →recent activity