← previous blocknext block →recent activity
Analyzing
Block #95,155,729
21 transactions · 20 stateful · 2026-08-11 20:23:08 UTC
Parallelism
67/100
Blocked
60%
Avg conflicts / tx
1.48
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,155,729 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w59w612w013w114w215w316w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6e37efb…afc2
0xe52b14…7230
12 touches
15 conflicts
0xa6e37efb…afc0
0xe52b14…7230
12 touches
15 conflicts
0xe1902c61…65ad
0xe52b14…7230
12 touches
15 conflicts
0xe1902c61…65af
0xe52b14…7230
12 touches
15 conflicts
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0xac4e7d69…252d
0xe52b14…7230
11 touches
15 conflicts
0xbde524f4…43bf
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
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: 0xe52b1424…bb7230
15 conflicts on slot 0xa6e37efb84…caafc2
Audit this contract →
← previous block·next block →recent activity