← previous blocknext block →recent activity
Analyzing
Block #95,202,980
25 transactions · 24 stateful · 2026-08-12 00:20:47 UTC
Parallelism
80/100
Blocked
46%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,202,980 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w09w010w111w112w214w316w417w118w223w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x503d17fc…e0a9
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0x7ac265cd…0253
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x24b08f9c…e594
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x96dd83e6…a507
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x503d17fcf8…40e0a9
Audit this contract →
← previous block·next block →recent activity