← previous blocknext block →recent activity
Analyzing
Block #93,490,596
21 transactions · 20 stateful · 2026-08-06 00:30:18 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,490,596 · 21 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
1w03w15w07w08w19w210w311w412w515w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x4e8c4408…d37b
0x34b655…2a6f
6 touches
3 conflicts
0x64f1eb47…cd27
0x34b655…2a6f
6 touches
3 conflicts
0x4e8c4408…d37a
0x34b655…2a6f
6 touches
3 conflicts
0x19795ad6…4a16
0x34b655…2a6f
6 touches
3 conflicts
0x98d64054…e0f2
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity