← previous blocknext block →recent activity
Analyzing
Block #95,125,612
14 transactions · 13 stateful · 2026-08-11 17:51:39 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,125,612 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf83843c9…7068
0xe52b14…7230
8 touches
6 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
8 touches
6 conflicts
0x3845e7dc…c691
0xe52b14…7230
8 touches
6 conflicts
0xf79df061…e005
0xe52b14…7230
8 touches
6 conflicts
0x4100d6d1…4248
0xe52b14…7230
6 touches
6 conflicts
0x1be9b382…2a5e
0xe52b14…7230
6 touches
3 conflicts
0x5222cecc…97d2
0xe52b14…7230
5 touches
3 conflicts
0x740994f6…5bcb
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xf83843c9b9…a57068
Audit this contract →
← previous block·next block →recent activity