← previous blocknext block →recent activity
Analyzing
Block #86,157,107
24 transactions · 20 stateful · 2026-07-07 08:33:19 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,157,107 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w07w18w213w319w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b2f3e6d…978f
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xfa826c51…c762
0x34b655…2a6f
6 touches
3 conflicts
0x3a7fb5b5…f0e5
0x34b655…2a6f
6 touches
3 conflicts
0x456f4453…91f0
0x34b655…2a6f
6 touches
3 conflicts
0x4d658fb7…ed44
0x34b655…2a6f
6 touches
3 conflicts
0x65903ef9…2567
0x34b655…2a6f
6 touches
3 conflicts
0xb245fe36…d765
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x7b2f3e6d7d…4d978f
Audit this contract →
← previous block·next block →recent activity