← previous blocknext block →recent activity
Analyzing
Block #100,066,097
58 transactions · 54 stateful · 2026-08-29 02:33:05 UTC
Parallelism
57/100
Blocked
78%
Avg conflicts / tx
3.95
Longest chain
25 deep
Execution timeline
did this block parallelize well?
view
block #100,066,097 · 58 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
1w02w13w24w35w46w57w630w733w845w1348w1649w1754w22
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
32 touches
120 conflicts
0x75dcd88e…e643
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001c
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002c
0x1b6862…e19c
12 touches
15 conflicts
0x0f94ee4c…189b
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 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
120 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity