← previous blocknext block →recent activity
Analyzing
Block #93,136,264
20 transactions · 20 stateful · 2026-08-04 18:48:45 UTC
Parallelism
70/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,136,264 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w16w37w013w414w115w218w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99f666e3…b2a2
0x3bd359…433a
6 touches
3 conflicts
0x9194f4a3…10b8
0x754704…b603
6 touches
3 conflicts
0x00000000…0000
0xfa32f9…f3f0
6 touches
3 conflicts
0x00000000…0001
0xfa32f9…f3f0
6 touches
3 conflicts
0x93681d59…5918
0xfa32f9…f3f0
6 touches
3 conflicts
0xe72ac8f1…9541
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x0747620e…977f
0x1b6862…e19c
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: Wrapped MON (WMON)
3 conflicts on slot 0x99f666e3cf…76b2a2
Audit this contract →
← previous block·next block →recent activity