← previous blocknext block →recent activity
Analyzing
Block #86,493,599
17 transactions · 13 stateful · 2026-07-08 22:01:04 UTC
Parallelism
71/100
Blocked
46%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,493,599 · 17 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
1w03w14w07w08w19w212w114w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02c4bb0f…f2c8
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
4 touches
1 conflict
0x0d42a59b…df19
0x34b655…2a6f
4 touches
1 conflict
0x0dd44476…ef40
0x34b655…2a6f
4 touches
1 conflict
0x3a2adaa6…51c2
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
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
3 conflicts on slot 0x02c4bb0f0a…d0f2c8
Audit this contract →
← previous block·next block →recent activity