← previous blocknext block →recent activity
Analyzing
Block #95,075,600
33 transactions · 31 stateful · 2026-08-11 13:40:03 UTC
Parallelism
55/100
Blocked
74%
Avg conflicts / tx
2.55
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #95,075,600 · 33 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w16w27w08w39w110w411w512w614w215w118w620w721w826w827w928w1029w1130w1231w1332w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0d45ffd…89cf
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0xec7d120d…7084
0x34b655…2a6f
10 touches
10 conflicts
0xac3e4969…39e9
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
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
21 conflicts on slot 0xf0d45ffdb0…4089cf
Audit this contract →
← previous block·next block →recent activity