← previous blocknext block →recent activity
Analyzing
Block #95,128,794
53 transactions · 48 stateful · 2026-08-11 18:07:39 UTC
Parallelism
66/100
Blocked
73%
Avg conflicts / tx
2.53
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #95,128,794 · 53 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w18w29w310w411w012w213w316w317w436w941w242w143w344w447w1251w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
16 touches
28 conflicts
0x4c188934…158e
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0xeae24c…0be0
10 touches
10 conflicts
0xa56e54d0…2d39
0x34b655…2a6f
10 touches
10 conflicts
0xbde524f4…43bf
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xe8eae8a3…bacc
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
28 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity