← previous blocknext block →recent activity
Analyzing
Block #87,718,498
25 transactions · 20 stateful · 2026-07-14 14:33:03 UTC
Parallelism
84/100
Blocked
20%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,718,498 · 25 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
1w05w06w111w017w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc573ca73…fcd2
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x6d85c11e…9c54
0x34b655…2a6f
6 touches
3 conflicts
0x0a750e9d…870b
0x34b655…2a6f
4 touches
1 conflict
0x24b6091e…d294
0x34b655…2a6f
4 touches
1 conflict
0x27b9caf2…c102
0x34b655…2a6f
4 touches
1 conflict
0x3095aa84…e9e3
0x34b655…2a6f
4 touches
1 conflict
0x36890fff…f3d1
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 0xc573ca736f…98fcd2
Audit this contract →
← previous block·next block →recent activity