← previous blocknext block →recent activity
Analyzing
Block #86,299,935
21 transactions · 18 stateful · 2026-07-08 00:26:52 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,299,935 · 21 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
7w08w19w010w111w213w314w015w116w018w119w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c806a17…a094
0x34b655…2a6f
6 touches
3 conflicts
0x0672e4a2…8d1f
0x34b655…2a6f
6 touches
3 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6c73c136…2ca1
0x34b655…2a6f
4 touches
1 conflict
0xb03ccb40…ede4
0x34b655…2a6f
4 touches
1 conflict
0xbe9baf16…df37
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 0x5c806a17a4…85a094
Audit this contract →
← previous block·next block →recent activity