← previous blocknext block →recent activity
Analyzing
Block #87,703,459
15 transactions · 14 stateful · 2026-07-14 12:52:12 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,703,459 · 15 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
2w03w14w28w19w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x5c591136…d322
0x34b655…2a6f
6 touches
3 conflicts
0x5170a218…3a84
0xc8689a…ee79
4 touches
1 conflict
0x239122db…dc81
0x34b655…2a6f
4 touches
1 conflict
0x410b84ab…1dbc
0x34b655…2a6f
4 touches
1 conflict
0xb11a3969…fc6a
0x34b655…2a6f
4 touches
1 conflict
0xe1fe8278…8591
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity