← previous blocknext block →recent activity
Analyzing
Block #95,570,081
19 transactions · 16 stateful · 2026-08-13 07:20:49 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,570,081 · 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
2w03w18w29w010w011w112w013w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2840c278…bbc7
0x34b655…2a6f
8 touches
6 conflicts
0x671fcc71…2ddb
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x43fd3667…094b
0x34b655…2a6f
4 touches
1 conflict
0x91cf9f4c…5b4f
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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
6 conflicts on slot 0x2840c278a3…01bbc7
Audit this contract →
← previous block·next block →recent activity