← previous blocknext block →recent activity
Analyzing
Block #85,494,973
17 transactions · 17 stateful · 2026-07-04 06:59:05 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,494,973 · 17 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
1w02w110w011w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0eac6378…36f4
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x070a562a…8147
0x34b655…2a6f
4 touches
1 conflict
0x1ba201e6…08f5
0x40c49f…2af0
2 touches
0 conflicts
0x2ec6aa9d…7da4
0x40c49f…2af0
2 touches
0 conflicts
0x4267e9d4…43ae
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 0x0eac637818…cb36f4
Audit this contract →
← previous block·next block →recent activity