← previous blocknext block →recent activity
Analyzing
Block #87,754,446
14 transactions · 14 stateful · 2026-07-14 18:33:31 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,754,446 · 14 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
1w07w08w19w211w113w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xddaf39ca…9bd5
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x10981d9e…6ebc
0x34b655…2a6f
4 touches
1 conflict
0x34bcdc05…6689
0x34b655…2a6f
4 touches
1 conflict
0x36223362…c0ce
0x34b655…2a6f
4 touches
1 conflict
0x40080907…45cc
0x34b655…2a6f
4 touches
1 conflict
0x4f92c64e…9adc
0x34b655…2a6f
4 touches
1 conflict
0x595cbd16…dac4
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
6 conflicts on slot 0xddaf39ca4a…3c9bd5
Audit this contract →
← previous block·next block →recent activity