← previous blocknext block →recent activity
Analyzing
Block #93,681,666
13 transactions · 13 stateful · 2026-08-06 16:30:50 UTC
Parallelism
69/100
Blocked
54%
Avg conflicts / tx
0.92
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,681,666 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w17w08w19w210w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x511ce9e9…71f0
0x968279…9342
6 touches
3 conflicts
0x017a5a4e…a2e5
0x968279…9342
6 touches
3 conflicts
0x511ce9e9…71ed
0x968279…9342
6 touches
3 conflicts
0x511ce9e9…71ee
0x968279…9342
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 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: Perpl
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity