← previous blocknext block →recent activity
Analyzing
Block #92,770,072
10 transactions · 10 stateful · 2026-08-03 12:05:06 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,770,072 · 10 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1af53e83…c72e
0x754704…b603
4 touches
1 conflict
0x37e1e6f1…84d0
0x754704…b603
4 touches
1 conflict
0x7e8cd4a2…8fc0
0x754704…b603
4 touches
1 conflict
0x13ec4c5f…a778
0x99c7a7…8bf0
4 touches
1 conflict
0xd930d57a…3bfb
0x99c7a7…8bf0
4 touches
1 conflict
0x2741bc7f…051d
0x34b655…2a6f
2 touches
0 conflicts
0x2e70e07e…48db
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e65
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: USDC (USDC)
1 conflict on slot 0x1af53e839b…15c72e
Audit this contract →
← previous block·next block →recent activity