← previous blocknext block →recent activity
Analyzing
Block #86,796,362
18 transactions · 13 stateful · 2026-07-10 07:46:21 UTC
Parallelism
78/100
Blocked
31%
Avg conflicts / tx
0.22
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,796,362 · 18 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
3w04w15w27w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5160d69…1619
0x34b655…2a6f
4 touches
1 conflict
0x07c94816…b666
0x34b655…2a6f
4 touches
1 conflict
0x07d94be1…7fa8
0x34b655…2a6f
4 touches
1 conflict
0xa6a8d7ce…d4f1
0x34b655…2a6f
4 touches
1 conflict
0xcfb9b777…5e1b
0x34b655…2a6f
4 touches
1 conflict
0xe549cb73…80c8
0x34b655…2a6f
4 touches
1 conflict
0xec2551de…e262
0x34b655…2a6f
4 touches
1 conflict
0xf2f4727d…cdb7
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 0xf5160d69e7…c01619
Audit this contract →
← previous block·next block →recent activity