← previous blocknext block →recent activity
Analyzing
Block #95,245,554
53 transactions · 46 stateful · 2026-08-12 03:57:20 UTC
Parallelism
62/100
Blocked
72%
Avg conflicts / tx
3.13
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #95,245,554 · 53 txs across 20 waves · depth 20
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
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w611w712w813w920w1026w1140w1241w1347w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
20 touches
45 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
14 touches
21 conflicts
0xafb8e71e…9285
0x34b655…2a6f
14 touches
21 conflicts
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0xbde524f4…43bf
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 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
45 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity