← previous blocknext block →recent activity
Analyzing
Block #95,180,978
34 transactions · 31 stateful · 2026-08-11 22:30:08 UTC
Parallelism
82/100
Blocked
68%
Avg conflicts / tx
1.38
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,180,978 · 34 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w18w310w411w012w113w214w326w129w430w531w532w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xeae24c…0be0
10 touches
10 conflicts
0x88cf9cea…080b
0xd32edf…ff58
9 touches
10 conflicts
0x35801c67…bcc0
0x1b6862…e19c
8 touches
6 conflicts
0x80afd9d9…57cf
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
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: 0xeae24c72…e30be0
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity