← previous blocknext block →recent activity
Analyzing
Block #100,144,516
23 transactions · 20 stateful · 2026-08-29 09:08:04 UTC
Parallelism
70/100
Blocked
60%
Avg conflicts / tx
1.61
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,144,516 · 23 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
1w02w13w24w36w17w28w39w412w513w615w417w522w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ed1f9d0…fc7f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c4
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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 0x5ed1f9d00b…62fc7f
Audit this contract →
← previous block·next block →recent activity