← previous blocknext block →recent activity
Analyzing
Block #86,663,512
14 transactions · 13 stateful · 2026-07-09 16:59:15 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,663,512 · 14 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
3w06w07w08w19w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb4cb196…8c4a
0x34b655…2a6f
4 touches
1 conflict
0x1c03f81f…b304
0x34b655…2a6f
4 touches
1 conflict
0x322dcd34…8718
0x34b655…2a6f
4 touches
1 conflict
0x3b5818bf…0d6d
0x34b655…2a6f
4 touches
1 conflict
0x453f53a8…e541
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x491b0c86…0eb3
0x34b655…2a6f
4 touches
1 conflict
0x5a36d0c8…12e2
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 0xfb4cb196b2…e68c4a
Audit this contract →
← previous block·next block →recent activity