← previous blocknext block →recent activity
Analyzing
Block #95,656,428
24 transactions · 20 stateful · 2026-08-13 14:35:09 UTC
Parallelism
83/100
Blocked
50%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,656,428 · 24 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
1w02w13w25w06w17w08w19w013w214w315w016w117w218w323w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf83843c9…706a
0xe52b14…7230
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf9849b1a…7ec8
0x34b655…2a6f
6 touches
3 conflicts
0x74c17a9f…3aeb
0xe52b14…7230
6 touches
3 conflicts
0xf3ab898f…a814
0xe52b14…7230
6 touches
3 conflicts
0xf3ab898f…a816
0xe52b14…7230
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
6 touches
3 conflicts
0xf83843c9…7068
0xe52b14…7230
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: 0xe52b1424…bb7230
3 conflicts on slot 0xf83843c9b9…a5706a
Audit this contract →
← previous block·next block →recent activity