← previous blocknext block →recent activity
Analyzing
Block #103,050,179
38 transactions · 34 stateful · 2026-09-08 13:22:38 UTC
Parallelism
82/100
Blocked
59%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #103,050,179 · 38 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w29w010w011w012w113w315w116w217w318w421w124w326w427w128w330w431w432w535w137w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x937a52a8…2719
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x55192654…91fe
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
6 touches
3 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
10 conflicts on slot 0x937a52a895…d12719
Audit this contract →
← previous block·next block →recent activity