← previous blocknext block →recent activity
Analyzing
Block #101,668,130
22 transactions · 20 stateful · 2026-09-03 16:58:03 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,668,130 · 22 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
1w03w14w05w06w17w08w114w215w316w218w319w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xdd6538fb…2b3f
0x34b655…2a6f
8 touches
6 conflicts
0x4ee0b65a…6d40
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xb409e204…89ac
0x34b655…2a6f
6 touches
3 conflicts
0x84f3a813…05c0
0x34b655…2a6f
6 touches
3 conflicts
0x20b1228b…2487
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity