← previous blocknext block →recent activity
Analyzing
Block #95,743,759
11 transactions · 9 stateful · 2026-08-13 21:55:26 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,743,759 · 11 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
5w06w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2210fbde…49cc
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0xba1edffb…323e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x169c4d09…f2a6
0x065c9d…c394
2 touches
0 conflicts
0x7be5def0…e9f8
0x065c9d…c394
2 touches
0 conflicts
0x7d330707…c625
0x065c9d…c394
2 touches
0 conflicts
0xe20cce39…6ada
0x065c9d…c394
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 0x2210fbde2a…3849cc
Audit this contract →
← previous block·next block →recent activity