← previous blocknext block →recent activity
Analyzing
Block #85,916,335
18 transactions · 16 stateful · 2026-07-06 05:46:11 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,916,335 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w05w17w18w210w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1aaf4996…65ec
0x34b655…2a6f
6 touches
3 conflicts
0xe06bbb2e…9417
0x34b655…2a6f
6 touches
3 conflicts
0xe06bbb2e…9416
0x34b655…2a6f
6 touches
3 conflicts
0x684738fb…0fe7
0x34b655…2a6f
5 touches
3 conflicts
0x7e4b5149…c444
0x34b655…2a6f
4 touches
1 conflict
0x9a3463f0…0b73
0x34b655…2a6f
4 touches
1 conflict
0xaa3c398a…05d0
0x34b655…2a6f
4 touches
1 conflict
0xab9066ad…6d83
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 0x1aaf499609…4665ec
Audit this contract →
← previous block·next block →recent activity