← previous blocknext block →recent activity
Analyzing
Block #93,447,054
10 transactions · 10 stateful · 2026-08-05 20:51:25 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,447,054 · 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
0x2edbccf6…cc14
0x754704…b603
4 touches
1 conflict
0x768de509…bf9b
0x754704…b603
4 touches
1 conflict
0x140bbe18…6f47
0x99c7a7…8bf0
4 touches
1 conflict
0xa5b2d571…e945
0x99c7a7…8bf0
4 touches
1 conflict
0x1ea2c53b…887a
0x754704…b603
4 touches
1 conflict
0x57c874be…de5b
0xea1b8e…c5ec
2 touches
0 conflicts
0xb6b74ae0…8d5e
0xea1b8e…c5ec
2 touches
0 conflicts
0xd8eb2d31…2ac0
0xea1b8e…c5ec
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 0x2edbccf645…eacc14
Audit this contract →
← previous block·next block →recent activity