← previous blocknext block →recent activity
Analyzing
Block #103,212,658
18 transactions · 17 stateful · 2026-09-09 03:01:53 UTC
Parallelism
61/100
Blocked
35%
Avg conflicts / tx
0.61
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #103,212,658 · 18 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
5w07w19w210w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x76832384…dc5b
0x34b655…2a6f
4 touches
1 conflict
0x422d5490…52d9
0x34b655…2a6f
4 touches
1 conflict
0x22badbc6…4c24
0x34b655…2a6f
4 touches
1 conflict
0x48ed1159…abe9
0x34ae4d…3fc5
2 touches
0 conflicts
0x07b312ec…a1a9
0x34b655…2a6f
2 touches
0 conflicts
0x6f84ef84…787f
0x34b655…2a6f
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity