← previous blocknext block →recent activity
Analyzing
Block #95,714,920
12 transactions · 11 stateful · 2026-08-13 19:30:20 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,714,920 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07d94be1…7fa8
0x34b655…2a6f
6 touches
3 conflicts
0x17d85914…c075
0x34b655…2a6f
6 touches
3 conflicts
0x6cd18858…a7be
0x34b655…2a6f
6 touches
3 conflicts
0x9e15e7b9…9fdf
0x34b655…2a6f
6 touches
3 conflicts
0xa538ac07…fc9e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
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
3 conflicts on slot 0x07d94be17c…6a7fa8
Audit this contract →
← previous block·next block →recent activity