← previous blocknext block →recent activity
Analyzing
Block #85,679,678
9 transactions · 7 stateful · 2026-07-05 03:28:43 UTC
Parallelism
78/100
Blocked
43%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,679,678 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fd37234…2731
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x08de772c…8e84
0x2a68ba…90c5
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x2ab1d0e8…ad0b
0x40c49f…2af0
2 touches
0 conflicts
0x34401412…4cdc
0x40c49f…2af0
2 touches
0 conflicts
0x347556da…28eb
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
1 conflict on slot 0x9fd37234c4…602731
Audit this contract →
← previous block·next block →recent activity