← previous blocknext block →recent activity
Analyzing
Block #93,279,779
14 transactions · 13 stateful · 2026-08-05 06:50:24 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,279,779 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w17w210w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6cafaca…cb5e
0x968279…9342
4 touches
1 conflict
0x6499e0b9…9339
0x968279…9342
4 touches
1 conflict
0x6499e0b9…933b
0x968279…9342
4 touches
1 conflict
0xd6cafaca…cb5b
0x968279…9342
4 touches
1 conflict
0xd6cafaca…cb5c
0x968279…9342
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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: 0x96827978…f09342
1 conflict on slot 0xd6cafaca5a…56cb5e
Audit this contract →
← previous block·next block →recent activity