← previous blocknext block →recent activity
Analyzing
Block #95,246,020
6 transactions · 5 stateful · 2026-08-12 04:00:45 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,246,020 · 6 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49611dcc…9864
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0d0a5a38…1637
0x34b655…2a6f
2 touches
0 conflicts
0x1526b11f…8b21
0x34b655…2a6f
2 touches
0 conflicts
0x1b1f463f…401a
0x34b655…2a6f
2 touches
0 conflicts
0x24b08f9c…e594
0x34b655…2a6f
2 touches
0 conflicts
0x32b804b3…ce18
0x34b655…2a6f
2 touches
0 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: Perpl
1 conflict on slot 0x49611dccc0…579864
Audit this contract →
← previous block·next block →recent activity