← previous blocknext block →recent activity
Analyzing
Block #87,786,625
16 transactions · 15 stateful · 2026-07-14 22:08:47 UTC
Parallelism
56/100
Blocked
53%
Avg conflicts / tx
1.19
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,786,625 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w48w09w110w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c0795f1…c252
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xa80684c9…3948
0x34b655…2a6f
8 touches
6 conflicts
0x20ff72d4…5971
0x34b655…2a6f
7 touches
6 conflicts
0x3fde350e…8d43
0x34b655…2a6f
6 touches
3 conflicts
0x5170a218…3a84
0xc8689a…ee79
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x2549dda6…9e24
0x34b655…2a6f
6 touches
3 conflicts
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
6 conflicts on slot 0x7c0795f155…d0c252
Audit this contract →
← previous block·next block →recent activity