← previous blocknext block →recent activity
Analyzing
Block #100,082,180
32 transactions · 30 stateful · 2026-08-29 03:54:04 UTC
Parallelism
63/100
Blocked
67%
Avg conflicts / tx
1.69
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #100,082,180 · 32 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w210w211w012w313w415w516w617w721w323w424w226w928w430w1031w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd37a0e4…77ed
0x34b655…2a6f
12 touches
15 conflicts
0xfb14d7f1…e509
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0x1f8a126c…9aa5
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x3e6302c8…64f5
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
15 conflicts on slot 0xbd37a0e4d7…fe77ed
Audit this contract →
← previous block·next block →recent activity