← previous blocknext block →recent activity
Analyzing
Block #95,216,414
24 transactions · 21 stateful · 2026-08-12 01:28:21 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,216,414 · 24 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
3w04w05w17w08w19w210w311w012w113w214w315w416w420w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6e37efb…afc0
0xe52b14…7230
10 touches
10 conflicts
0xf79df061…e005
0xe52b14…7230
10 touches
10 conflicts
0xb1218965…e321
0xe52b14…7230
10 touches
10 conflicts
0xa6e37efb…afc2
0xe52b14…7230
10 touches
10 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
10 touches
10 conflicts
0x51232c8c…f30c
0xe52b14…7230
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x2b54cadb…4425
0xd18b7e…414b
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
10 conflicts on slot 0xa6e37efb84…caafc0
Audit this contract →
← previous block·next block →recent activity