← previous blocknext block →recent activity
Analyzing
Block #86,513,788
9 transactions · 9 stateful · 2026-07-09 00:15:42 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,513,788 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfefb0189…f726
0x34b655…2a6f
4 touches
1 conflict
0x4e0706c0…c4d1
0x34b655…2a6f
4 touches
1 conflict
0x79e8f935…c3b6
0x34b655…2a6f
4 touches
1 conflict
0x2b7fc28c…d175
0x065c9d…c394
2 touches
0 conflicts
0x554cc4a8…9e94
0x065c9d…c394
2 touches
0 conflicts
0xc3d44f79…a3c2
0x065c9d…c394
2 touches
0 conflicts
0xcab36dd6…82dd
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
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 0xfefb01895a…9bf726
Audit this contract →
← previous block·next block →recent activity