← previous blocknext block →recent activity
Analyzing
Block #93,666,944
15 transactions · 13 stateful · 2026-08-06 15:16:49 UTC
Parallelism
87/100
Blocked
31%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,666,944 · 15 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
3w04w16w17w08w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x69a45f39…39aa
0x34b655…2a6f
4 touches
1 conflict
0x3f5f366d…10d9
0x34b655…2a6f
2 touches
0 conflicts
0x5ae4ce47…6322
0x34b655…2a6f
2 touches
0 conflicts
0x809f2ba8…89d3
0x34b655…2a6f
2 touches
0 conflicts
0x953517cb…cdec
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity