← previous blocknext block →recent activity
Analyzing
Block #101,020,998
20 transactions · 17 stateful · 2026-09-01 10:41:55 UTC
Parallelism
75/100
Blocked
41%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,020,998 · 20 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
1w02w13w210w011w112w213w315w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9dccd2a9…2790
0x34b655…2a6f
10 touches
10 conflicts
0x37119f33…8344
0x34b655…2a6f
8 touches
6 conflicts
0xf47c461d…a5b6
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x2bbc0cfb…c2c2
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
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 0x9dccd2a98b…6d2790
Audit this contract →
← previous block·next block →recent activity