← previous blocknext block →recent activity
Analyzing
Block #95,977,590
21 transactions · 18 stateful · 2026-08-14 17:31:53 UTC
Parallelism
76/100
Blocked
67%
Avg conflicts / tx
1.1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,977,590 · 21 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
1w03w14w25w36w17w28w39w314w415w016w117w218w420w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x640fd1c6…d624
0x34b655…2a6f
8 touches
6 conflicts
0xa0d3a786…91d9
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xc363ff23…e97e
0x968279…9342
6 touches
3 conflicts
0x40856fd2…0eb9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc363ff23…e977
0x968279…9342
6 touches
3 conflicts
0xc363ff23…e978
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: Perpl
6 conflicts on slot 0x640fd1c6c3…c0d624
Audit this contract →
← previous block·next block →recent activity