← previous blocknext block →recent activity
Analyzing
Block #93,313,748
16 transactions · 13 stateful · 2026-08-05 09:41:11 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,313,748 · 16 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
2w03w15w06w110w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1803586e…d149
0xa6afd3…d132
4 touches
1 conflict
0x25b1eaa5…e2e6
0x968279…9342
4 touches
1 conflict
0x25b1eaa5…e2e7
0x968279…9342
4 touches
1 conflict
0x3b3f1a95…7705
0x968279…9342
4 touches
1 conflict
0x3b3f1a95…7706
0x968279…9342
4 touches
1 conflict
0x3b3f1a95…7708
0x968279…9342
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
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: Kuru Exchange: Market-WETH/USDC
1 conflict on slot 0x1803586e82…92d149
Audit this contract →
← previous block·next block →recent activity