← previous blocknext block →recent activity
Analyzing
Block #93,239,115
12 transactions · 10 stateful · 2026-08-05 03:25:56 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,239,115 · 12 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
2w03w15w06w17w28w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5bc53470…8dde
0x34b655…2a6f
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xfe2a4afa…5141
0x968279…9342
4 touches
1 conflict
0xa86351b8…2c5a
0x34b655…2a6f
4 touches
1 conflict
0xb9f0b0dc…4827
0x34b655…2a6f
4 touches
1 conflict
0xfe2a4afa…513a
0x968279…9342
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
3 conflicts on slot 0x5bc534701b…af8dde
Audit this contract →
← previous block·next block →recent activity