← previous blocknext block →recent activity
Analyzing
Block #93,579,703
36 transactions · 28 stateful · 2026-08-06 07:58:14 UTC
Parallelism
86/100
Blocked
61%
Avg conflicts / tx
1.03
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,579,703 · 36 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
1w02w13w25w07w19w310w212w015w117w218w320w427w228w329w430w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x91855e…ac7e
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x5fde6655…f244
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x439cfb2c…7b9e
0xa6afd3…d132
6 touches
3 conflicts
0x89678d1b…463e
0xa6afd3…d132
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: 0x91855e79…58ac7e
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity