← previous blocknext block →recent activity
Analyzing
Block #85,902,069
13 transactions · 9 stateful · 2026-07-06 04:11:12 UTC
Parallelism
85/100
Blocked
11%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,902,069 · 13 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
1w02w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x667658e1…e172
0x34b655…2a6f
4 touches
1 conflict
0xb274cb13…808b
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
2 touches
0 conflicts
0x3a5c445f…7255
0x34b655…2a6f
2 touches
0 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
2 touches
0 conflicts
0x7ce5dfc7…887e
0x34b655…2a6f
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 0x667658e1ed…4de172
Audit this contract →
← previous block·next block →recent activity