← previous blocknext block →recent activity
Analyzing
Block #95,737,767
16 transactions · 13 stateful · 2026-08-13 21:25:18 UTC
Parallelism
63/100
Blocked
54%
Avg conflicts / tx
1.19
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,737,767 · 16 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
1w03w04w15w18w09w210w311w012w413w115w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c8753e8…d214
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x08636046…e60f
0x34b655…2a6f
6 touches
3 conflicts
0xfdeee566…3263
0x34b655…2a6f
6 touches
3 conflicts
0x0abf7b77…0d80
0x34b655…2a6f
4 touches
1 conflict
0x757b0543…e087
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
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 0x1c8753e8cf…47d214
Audit this contract →
← previous block·next block →recent activity