← previous blocknext block →recent activity
Analyzing
Block #100,142,171
23 transactions · 23 stateful · 2026-08-29 08:56:16 UTC
Parallelism
52/100
Blocked
65%
Avg conflicts / tx
2.43
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #100,142,171 · 23 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w29w312w413w514w615w716w817w920w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76899ea6…e60a
0x34b655…2a6f
16 touches
28 conflicts
0xa11b60f7…8e8b
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0xd18a8dca…452e
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
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
28 conflicts on slot 0x76899ea6bf…75e60a
Audit this contract →
← previous block·next block →recent activity