← previous blocknext block →recent activity
Analyzing
Block #95,864,043
16 transactions · 12 stateful · 2026-08-14 08:00:25 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,864,043 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w18w29w311w413w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31616f97…1acc
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x56153262…21ce
0x34b655…2a6f
4 touches
1 conflict
0x6bdc9bd4…1989
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xc0df898b…1ee6
0x065c9d…c394
3 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0028
0x1b6862…e19c
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
3 conflicts on slot 0x31616f9701…df1acc
Audit this contract →
← previous block·next block →recent activity