← previous blocknext block →recent activity
Analyzing
Block #95,413,192
9 transactions · 8 stateful · 2026-08-12 18:11:27 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,413,192 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd96e9b43…2a27
0x34b655…2a6f
6 touches
3 conflicts
0x05527801…9c11
0x34b655…2a6f
6 touches
3 conflicts
0xa09b2b70…8ff9
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xd459bf7b…92c3
0x34b655…2a6f
4 touches
1 conflict
0xe5b1fe83…1af5
0x34b655…2a6f
4 touches
1 conflict
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
3 conflicts on slot 0xd96e9b43fd…312a27
Audit this contract →
← previous block·next block →recent activity