← previous blocknext block →recent activity
Analyzing
Block #95,720,961
20 transactions · 19 stateful · 2026-08-13 20:00:47 UTC
Parallelism
75/100
Blocked
37%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,720,961 · 20 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
8w09w110w211w012w113w214w315w417w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0008
0x0ea966…0742
10 touches
10 conflicts
0x724cd9ff…6684
0xe4f6e7…9657
10 touches
10 conflicts
0x44ad89ba…cf83
0xe4f6e7…9657
10 touches
10 conflicts
0x724cd9ff…6684
0x0cc9b2…7777
10 touches
10 conflicts
0xa49a8ead…c1a6
0x968279…9342
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0xfddf16c6…4ce6
0x968279…9342
6 touches
3 conflicts
0xfddf16c6…4ce7
0x968279…9342
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: 0x0ea96615…ff0742
10 conflicts on slot 0x0000000000…000008
Audit this contract →
← previous block·next block →recent activity