← previous blocknext block →recent activity
Analyzing
Block #95,405,015
19 transactions · 17 stateful · 2026-08-12 17:30:02 UTC
Parallelism
79/100
Blocked
18%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,405,015 · 19 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
3w04w06w111w012w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0b7842b…9379
0x34b655…2a6f
8 touches
6 conflicts
0x08636046…e60f
0x34b655…2a6f
6 touches
3 conflicts
0xafb8e71e…9285
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x226ae29a…2612
0x34b655…2a6f
4 touches
1 conflict
0x3b299648…f5cf
0x34b655…2a6f
4 touches
1 conflict
0x63759c44…7f20
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 0xb0b7842b5c…359379
Audit this contract →
← previous block·next block →recent activity