← previous blocknext block →recent activity
Analyzing
Block #95,726,821
19 transactions · 16 stateful · 2026-08-13 20:30:15 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,726,821 · 19 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
4w05w16w17w210w011w013w114w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08636046…e60f
0x34b655…2a6f
6 touches
3 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
6 touches
3 conflicts
0xadd8b6ed…e945
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x071163fa…f7db
0x34b655…2a6f
4 touches
1 conflict
0x00ddbbf2…4588
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: Perpl
3 conflicts on slot 0x08636046fc…69e60f
Audit this contract →
← previous block·next block →recent activity