← previous blocknext block →recent activity
Analyzing
Block #93,241,226
25 transactions · 24 stateful · 2026-08-05 03:36:33 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
1.04
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,241,226 · 25 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
2w03w15w06w17w28w39w010w111w012w113w216w317w218w320w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x91855e…ac7e
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x3de775b2…319b
0xa6afd3…d132
8 touches
6 conflicts
0xfa551be3…a911
0xa6afd3…d132
6 touches
3 conflicts
0xf9e23360…8ef7
0x34b655…2a6f
6 touches
3 conflicts
0xa86351b8…2c5a
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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: 0x91855e79…58ac7e
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity