← previous blocknext block →recent activity
Analyzing
Block #95,075,018
34 transactions · 33 stateful · 2026-08-11 13:37:08 UTC
Parallelism
53/100
Blocked
70%
Avg conflicts / tx
3.06
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #95,075,018 · 34 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w06w17w28w19w310w211w412w316w717w821w1025w226w329w1230w1333w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafb8e71e…9285
0x34b655…2a6f
16 touches
28 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
16 touches
28 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
12 touches
15 conflicts
0xec7d120d…7084
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x3ebb403d…3a8f
0x34b655…2a6f
8 touches
6 conflicts
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 0xafb8e71eb0…ec9285
Audit this contract →
← previous block·next block →recent activity