← previous blocknext block →recent activity
Analyzing
Block #100,140,400
39 transactions · 30 stateful · 2026-08-29 08:47:21 UTC
Parallelism
82/100
Blocked
60%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,140,400 · 39 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
1w02w13w24w35w46w37w08w112w013w120w021w127w530w331w432w534w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b7ad72e…a3d7
0x34b655…2a6f
12 touches
15 conflicts
0x97f0996a…3727
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0xd8d828a7…b64d
0x1b6862…e19c
10 touches
10 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 0x7b7ad72e57…7ba3d7
Audit this contract →
← previous block·next block →recent activity