← previous blocknext block →recent activity
Analyzing
Block #95,392,113
19 transactions · 18 stateful · 2026-08-12 16:24:47 UTC
Parallelism
84/100
Blocked
17%
Avg conflicts / tx
0.32
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,392,113 · 19 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
1w03w14w06w07w010w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf66c076…62fb
0x34b655…2a6f
6 touches
3 conflicts
0x3c0e49c9…7833
0x34b655…2a6f
4 touches
1 conflict
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0x66d5e476…8a1f
0x34b655…2a6f
4 touches
1 conflict
0x6771eae2…7014
0x34b655…2a6f
4 touches
1 conflict
0x69ee34d1…30f8
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xa87a4f4d…046e
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 0xbf66c07623…f462fb
Audit this contract →
← previous block·next block →recent activity