← previous blocknext block →recent activity
Analyzing
Block #95,550,066
15 transactions · 14 stateful · 2026-08-13 05:40:10 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,550,066 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w06w18w29w010w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbaccbe2b…e717
0x968279…9342
4 touches
1 conflict
0x5a025f2b…8de1
0x968279…9342
4 touches
1 conflict
0x5a025f2b…8de2
0x968279…9342
4 touches
1 conflict
0x5a025f2b…8de3
0x968279…9342
4 touches
1 conflict
0xbaccbe2b…e714
0x968279…9342
4 touches
1 conflict
0xbaccbe2b…e715
0x968279…9342
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
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: 0x96827978…f09342
1 conflict on slot 0xbaccbe2ba5…f4e717
Audit this contract →
← previous block·next block →recent activity