← previous blocknext block →recent activity
Analyzing
Block #93,553,469
10 transactions · 9 stateful · 2026-08-06 05:46:22 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,553,469 · 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
0x7f03e539…f4cc
0x754704…b603
4 touches
1 conflict
0xb50a217e…5384
0x754704…b603
4 touches
1 conflict
0xe50f87d9…047c
0x754704…b603
4 touches
1 conflict
0x4020f55f…a2b8
0x99c7a7…8bf0
4 touches
1 conflict
0xb8b0f02e…dea5
0x99c7a7…8bf0
4 touches
1 conflict
0x3b2c8363…a429
0x34b655…2a6f
2 touches
0 conflicts
0x3fff7ccd…5a48
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
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 0x7f03e53912…eef4cc
Audit this contract →
← previous block·next block →recent activity