← previous blocknext block →recent activity
Analyzing
Block #85,174,139
15 transactions · 13 stateful · 2026-07-02 19:22:11 UTC
Parallelism
53/100
Blocked
54%
Avg conflicts / tx
0.87
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,174,139 · 15 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w07w110w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2207d3d…59ce
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x9966da31…0d0f
0x34b655…2a6f
6 touches
3 conflicts
0xc640f46e…a538
0x34b655…2a6f
6 touches
3 conflicts
0xd7345835…5bb7
0x34b655…2a6f
6 touches
3 conflicts
0xdb58340f…7c8b
0x34b655…2a6f
6 touches
3 conflicts
0xf7e59d30…11dd
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 0xc2207d3d4e…b259ce
Audit this contract →
← previous block·next block →recent activity