← previous blocknext block →recent activity
Analyzing
Block #93,522,034
10 transactions · 9 stateful · 2026-08-06 03:08:21 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,522,034 · 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
2w03w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a473699…6159
0x754704…b603
4 touches
1 conflict
0x8434d4d0…d5d8
0x754704…b603
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x1c795b3a…8e8a
0x754704…b603
4 touches
1 conflict
0x04a32684…1017
0x99c7a7…8bf0
4 touches
1 conflict
0x7445e790…b2fc
0x99c7a7…8bf0
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
2 touches
0 conflicts
0xa020506f…7c60
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 0x3a4736997f…b06159
Audit this contract →
← previous block·next block →recent activity