← previous blocknext block →recent activity
Analyzing
Block #100,590,400
21 transactions · 21 stateful · 2026-08-30 22:35:23 UTC
Parallelism
76/100
Blocked
52%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,590,400 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w27w08w19w010w311w412w213w119w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd40c84d8…a02f
0x34b655…2a6f
8 touches
6 conflicts
0x9ef9caab…9c45
0x34b655…2a6f
8 touches
6 conflicts
0x1b2282b6…3227
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c5
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x14fe1598…d0ba
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xd40c84d868…d1a02f
Audit this contract →
← previous block·next block →recent activity