← previous blocknext block →recent activity
Analyzing
Block #103,222,964
24 transactions · 19 stateful · 2026-09-09 03:53:48 UTC
Parallelism
83/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #103,222,964 · 24 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
1w02w14w26w07w08w110w311w112w217w118w322w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x359866c7…de7b
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x47b8c918…bda1
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0xb31eb7d3…64eb
0xa6afd3…d132
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 0x359866c739…efde7b
Audit this contract →
← previous block·next block →recent activity