← previous blocknext block →recent activity
Analyzing
Block #95,554,224
20 transactions · 17 stateful · 2026-08-13 06:01:04 UTC
Parallelism
80/100
Blocked
24%
Avg conflicts / tx
0.2
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,554,224 · 20 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
2w03w04w112w213w316w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x007c19a0…3af4
0x34b655…2a6f
4 touches
1 conflict
0x2491d756…b71c
0xa6afd3…d132
4 touches
1 conflict
0x1526b11f…8b21
0x34b655…2a6f
4 touches
1 conflict
0x3b9bb58c…e73a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7be3246e…f89f
0x34b655…2a6f
4 touches
1 conflict
0xdb067026…9eb8
0x2b46c0…1669
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity