← previous blocknext block →recent activity
Analyzing
Block #95,214,302
22 transactions · 20 stateful · 2026-08-12 01:17:44 UTC
Parallelism
73/100
Blocked
50%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,214,302 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w08w19w210w011w112w213w314w415w517w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6e37efb…afc0
0xe52b14…7230
12 touches
15 conflicts
0x8ffa3328…ce11
0xe52b14…7230
12 touches
15 conflicts
0xe1902c61…65ad
0xe52b14…7230
12 touches
15 conflicts
0xa6e37efb…afc2
0xe52b14…7230
12 touches
15 conflicts
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0x48584cc4…f766
0xe52b14…7230
10 touches
15 conflicts
0xeae74f73…04f3
0x34b655…2a6f
8 touches
6 conflicts
0xbd9491f7…dd92
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…caafc0
Audit this contract →
← previous block·next block →recent activity