← previous blocknext block →recent activity
Analyzing
Block #95,555,728
13 transactions · 11 stateful · 2026-08-13 06:08:38 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,555,728 · 13 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
2w06w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x5d33617c…4a38
0x34b655…2a6f
4 touches
1 conflict
0x7be3246e…f89f
0x34b655…2a6f
4 touches
1 conflict
0xe3321cb6…26de
0x34b655…2a6f
4 touches
1 conflict
0xec2f37dc…e35f
0x34b655…2a6f
4 touches
1 conflict
0xee75c266…f8c6
0x34b655…2a6f
4 touches
1 conflict
0x7e3cc3e1…ced8
0x34b655…2a6f
4 touches
1 conflict
0x3727225e…a3cf
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity