← previous blocknext block →recent activity
Analyzing
Block #99,254,410
38 transactions · 31 stateful · 2026-08-26 06:13:20 UTC
Parallelism
79/100
Blocked
65%
Avg conflicts / tx
1.11
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,254,410 · 38 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w28w09w110w211w312w418w319w520w122w223w125w326w436w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x3e49348b…9445
0x34b655…2a6f
8 touches
6 conflicts
0xa33ea33a…9f49
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0x73912233…4585
0x1b6862…e19c
6 touches
3 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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity