← previous blocknext block →recent activity
Analyzing
Block #93,239,126
19 transactions · 15 stateful · 2026-08-05 03:25:59 UTC
Parallelism
84/100
Blocked
47%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,239,126 · 19 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
1w02w16w07w19w010w112w213w014w115w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d46e6a0…5ed9
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x52296782…74cc
0x40c49f…2af0
4 touches
1 conflict
0x00000000…0031
0x59df86…2780
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0x521a5982…a82a
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0x6a31053c…87f2
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: 0x40c49f17…d22af0
3 conflicts on slot 0x5d46e6a0b6…d15ed9
Audit this contract →
← previous block·next block →recent activity