← previous blocknext block →recent activity
Analyzing
Block #93,927,044
15 transactions · 14 stateful · 2026-08-07 13:04:53 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,927,044 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w36w07w18w29w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x116e7d…d8f1
8 touches
6 conflicts
0x00000000…0002
0x116e7d…d8f1
8 touches
6 conflicts
0x00000000…0003
0x116e7d…d8f1
8 touches
6 conflicts
0x44ad89ba…cf83
0x350035…7777
8 touches
6 conflicts
0x692a4122…76b8
0x350035…7777
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0xb7143610…adc4
0x3bd359…433a
8 touches
6 conflicts
0xa86351b8…2c5a
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: 0x116e7d07…d7d8f1
6 conflicts on slot 0x0000000000…000000
Audit this contract →
← previous block·next block →recent activity