← previous blocknext block →recent activity
Analyzing
Block #102,016,494
34 transactions · 34 stateful · 2026-09-04 22:15:33 UTC
Parallelism
50/100
Blocked
62%
Avg conflicts / tx
2.82
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #102,016,494 · 34 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w07w19w210w111w314w215w320w421w222w523w624w725w827w1028w1131w1433w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
8 touches
6 conflicts
0x70e677f5…e3bd
0x34b655…2a6f
8 touches
6 conflicts
0x36918c55…8424
0x34b655…2a6f
8 touches
6 conflicts
0x7dd96c96…7335
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity