← previous blocknext block →recent activity
Analyzing
Block #87,444,071
18 transactions · 17 stateful · 2026-07-13 07:56:50 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,444,071 · 18 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
4w06w09w110w215w216w317w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b353877…605d
0x34b655…2a6f
6 touches
3 conflicts
0xed7d2f2e…4b9d
0x34b655…2a6f
4 touches
1 conflict
0xf2112d98…bb04
0x34b655…2a6f
4 touches
1 conflict
0xf3fbc9b8…ab58
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x08cada97…a489
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
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 0x5b353877fb…57605d
Audit this contract →
← previous block·next block →recent activity