← previous blocknext block →recent activity
Analyzing
Block #95,115,277
16 transactions · 16 stateful · 2026-08-11 16:59:40 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.38
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,115,277 · 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
1w02w13w04w15w26w39w310w412w513w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0xa56e54d0…2d39
0x34b655…2a6f
10 touches
10 conflicts
0xce06a0f7…efef
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x5f453c44…fa94
0x34b655…2a6f
4 touches
1 conflict
0x75063279…0876
0x34b655…2a6f
4 touches
1 conflict
0x9bbb26e8…0d2e
0x99c7a7…8bf0
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
15 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity