← previous blocknext block →recent activity
Analyzing
Block #85,912,563
16 transactions · 15 stateful · 2026-07-06 05:21:02 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,912,563 · 16 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
2w03w05w07w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe33d8f47…b271
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0xcb89a818…e7c1
0x34b655…2a6f
4 touches
1 conflict
0x568090d5…d6b4
0x065c9d…c394
2 touches
0 conflicts
0x61c6d6fc…162e
0x065c9d…c394
2 touches
0 conflicts
0x70e160cc…2401
0x065c9d…c394
2 touches
0 conflicts
0x976251a0…23ac
0x065c9d…c394
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 0xe33d8f47f0…66b271
Audit this contract →
← previous block·next block →recent activity