← previous blocknext block →recent activity
Analyzing
Block #100,604,017
39 transactions · 29 stateful · 2026-08-30 23:43:54 UTC
Parallelism
77/100
Blocked
52%
Avg conflicts / tx
0.87
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,604,017 · 39 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w111w012w114w015w116w218w219w021w322w423w129w530w235w636w737w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x627738d1…db02
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x36918c55…8424
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd6370b2a…08cb
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
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
6 conflicts on slot 0x627738d150…b6db02
Audit this contract →
← previous block·next block →recent activity