← previous blocknext block →recent activity
Analyzing
Block #86,499,807
18 transactions · 14 stateful · 2026-07-08 22:42:28 UTC
Parallelism
72/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,499,807 · 18 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
2w03w14w05w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01a08f7d…dec6
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
4 touches
1 conflict
0xea8b9d6d…43da
0x34b655…2a6f
4 touches
1 conflict
0xed660153…a905
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x3483ab79…8ed3
0x34b655…2a6f
4 touches
1 conflict
0x4c214bb3…c5d3
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 0x01a08f7dea…2ddec6
Audit this contract →
← previous block·next block →recent activity