← previous blocknext block →recent activity
Analyzing
Block #95,541,110
18 transactions · 16 stateful · 2026-08-13 04:55:07 UTC
Parallelism
61/100
Blocked
56%
Avg conflicts / tx
1.39
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,541,110 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w17w28w09w110w211w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5f175ff…a0bd
0x968279…9342
14 touches
21 conflicts
0x521a5982…a82a
0x754704…b603
14 touches
21 conflicts
0x00000000…0006
0x968279…9342
14 touches
21 conflicts
0x64aaf87f…3b2a
0x968279…9342
14 touches
21 conflicts
0x64aaf87f…3b2b
0x968279…9342
14 touches
21 conflicts
0x64aaf87f…3b2d
0x968279…9342
14 touches
21 conflicts
0xe5f175ff…a0b6
0x968279…9342
14 touches
21 conflicts
0xe5f175ff…a0b7
0x968279…9342
14 touches
21 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
21 conflicts on slot 0xe5f175ffa7…06a0bd
Audit this contract →
← previous block·next block →recent activity