← previous blocknext block →recent activity
Analyzing
Block #100,151,846
69 transactions · 62 stateful · 2026-08-29 09:44:58 UTC
Parallelism
64/100
Blocked
77%
Avg conflicts / tx
4.59
Longest chain
25 deep
Execution timeline
did this block parallelize well?
view
block #100,151,846 · 69 txs across 25 waves · depth 25
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
wave w17
wave w18
wave w19
wave w20
wave w21
wave w22
wave w23
wave w24
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w26w415w516w617w718w836w938w1141w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
28 touches
91 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
26 touches
78 conflicts
0xce06de6e…4354
0xd32edf…ff58
23 touches
66 conflicts
0xca841faa…486a
0x34b655…2a6f
22 touches
55 conflicts
0x93afca4c…b47d
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…00c9
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 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
91 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity