← previous blocknext block →recent activity
Analyzing
Block #95,032,444
27 transactions · 25 stateful · 2026-08-11 10:02:11 UTC
Parallelism
81/100
Blocked
48%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,032,444 · 27 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
1w02w13w24w05w16w17w28w39w411w016w217w018w119w220w326w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99c0b00c…01f3
0x968279…9342
8 touches
6 conflicts
0x00000000…0006
0x968279…9342
8 touches
6 conflicts
0x0e618922…ae2f
0x968279…9342
8 touches
6 conflicts
0x0e618922…ae30
0x968279…9342
8 touches
6 conflicts
0x0e618922…ae33
0x968279…9342
8 touches
6 conflicts
0x0e618922…ae34
0x968279…9342
8 touches
6 conflicts
0x0e618922…ae36
0x968279…9342
8 touches
6 conflicts
0x99c0b00c…01f0
0x968279…9342
8 touches
6 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: 0x96827978…f09342
6 conflicts on slot 0x99c0b00cb8…5801f3
Audit this contract →
← previous block·next block →recent activity