← previous blocknext block →recent activity
Analyzing
Block #100,583,871
44 transactions · 41 stateful · 2026-08-30 22:02:33 UTC
Parallelism
61/100
Blocked
71%
Avg conflicts / tx
2.73
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #100,583,871 · 44 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
1w02w13w26w37w49w217w319w420w521w222w323w426w530w235w839w1240w1342w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xa3487cfd…b1eb
0xd32edf…ff58
11 touches
15 conflicts
0x3e49348b…9445
0x34b655…2a6f
10 touches
10 conflicts
0x359866c7…de7b
0x34b655…2a6f
10 touches
10 conflicts
0x9a100e05…c541
0x34b655…2a6f
8 touches
6 conflicts
0x261cbea7…e35d
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
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity