← previous blocknext block →recent activity
Analyzing
Block #95,728,411
14 transactions · 12 stateful · 2026-08-13 20:38:15 UTC
Parallelism
79/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,728,411 · 14 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
2w09w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35b0198e…3e0d
0x34b655…2a6f
4 touches
1 conflict
0x0dd3d3cd…7281
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0x5939780d…8d2a
0x34b655…2a6f
2 touches
0 conflicts
0xaba6578d…bd48
0x34b655…2a6f
2 touches
0 conflicts
0xb3fb9fb5…64db
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 0x35b0198ea3…413e0d
Audit this contract →
← previous block·next block →recent activity