← previous blocknext block →recent activity
Analyzing
Block #87,879,631
19 transactions · 14 stateful · 2026-07-15 08:30:51 UTC
Parallelism
84/100
Blocked
29%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,879,631 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w09w117w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf37c63b8…6da2
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe4636320…f407
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x4681609f…6493
0x34b655…2a6f
4 touches
1 conflict
0x4b2a19a6…fcf7
0x34b655…2a6f
4 touches
1 conflict
0x5a36d0c8…12e2
0x34b655…2a6f
4 touches
1 conflict
0x5a36d0c8…12e3
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
1 conflict on slot 0xf37c63b801…626da2
Audit this contract →
← previous block·next block →recent activity