← previous blocknext block →recent activity
Analyzing
Block #95,543,321
13 transactions · 11 stateful · 2026-08-13 05:06:14 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,543,321 · 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66d5e476…8a1f
0x34b655…2a6f
4 touches
1 conflict
0x8665471d…2214
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0672e4a2…8d1f
0x34b655…2a6f
2 touches
0 conflicts
0x1a82175f…9b38
0x34b655…2a6f
2 touches
0 conflicts
0x4615a47d…1c43
0x34b655…2a6f
2 touches
0 conflicts
0x4615a47d…1c44
0x34b655…2a6f
2 touches
0 conflicts
0x50e84e6c…287f
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 0x66d5e476c0…268a1f
Audit this contract →
← previous block·next block →recent activity