← previous blocknext block →recent activity
Analyzing
Block #102,284,250
23 transactions · 22 stateful · 2026-09-05 20:52:40 UTC
Parallelism
57/100
Blocked
55%
Avg conflicts / tx
2.17
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #102,284,250 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w110w114w215w317w418w519w620w721w822w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
18 touches
36 conflicts
0x51fc8795…126f
0x34b655…2a6f
18 touches
36 conflicts
0x7dd96c96…7335
0x34b655…2a6f
16 touches
28 conflicts
0x045532dd…4b7d
0x34b655…2a6f
8 touches
6 conflicts
0xba5743c7…21bf
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x0c842f86…0840
0x34b655…2a6f
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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity