← previous blocknext block →recent activity
Analyzing
Block #95,915,840
19 transactions · 19 stateful · 2026-08-14 12:21:14 UTC
Parallelism
58/100
Blocked
53%
Avg conflicts / tx
2.16
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #95,915,840 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w26w37w410w411w512w513w615w118w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
16 touches
28 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0xfb378fb4…bb46
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x07bb3f5a…617e
0x34b655…2a6f
6 touches
3 conflicts
0xe283e878…7262
0x34b655…2a6f
6 touches
3 conflicts
0xc0dedbc0…733c
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
28 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity