← previous blocknext block →recent activity
Analyzing
Block #87,489,709
20 transactions · 19 stateful · 2026-07-13 13:02:01 UTC
Parallelism
75/100
Blocked
58%
Avg conflicts / tx
1.25
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,489,709 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w16w17w28w010w111w312w213w314w315w417w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x5e5a350c…eb40
0x40c49f…2af0
6 touches
3 conflicts
0x88adad52…54b7
0x34b655…2a6f
6 touches
3 conflicts
0xb9266685…8b1d
0x34b655…2a6f
6 touches
3 conflicts
0xe4af56d6…5a50
0x34b655…2a6f
6 touches
3 conflicts
0xe9065ace…70fd
0x34b655…2a6f
6 touches
3 conflicts
0x09715d60…31f5
0x40c49f…2af0
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: 0x40c49f17…d22af0
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity