← previous blocknext block →recent activity
Analyzing
Block #85,160,181
9 transactions · 8 stateful · 2026-07-02 17:49:19 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,160,181 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2406ccf7…c1cb
0x34b655…2a6f
6 touches
3 conflicts
0x78e61184…39ec
0x34b655…2a6f
4 touches
1 conflict
0x8b1b058b…0435
0x34b655…2a6f
4 touches
1 conflict
0x5cc63a9e…5a55
0x34b655…2a6f
4 touches
1 conflict
0xd4260552…6422
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xd0806a61…8350
0x34b655…2a6f
4 touches
1 conflict
0x6a1c69df…4442
0x40c49f…2af0
2 touches
0 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
3 conflicts on slot 0x2406ccf7d1…d8c1cb
Audit this contract →
← previous block·next block →recent activity