← previous blocknext block →recent activity
Analyzing
Block #101,022,436
25 transactions · 25 stateful · 2026-09-01 10:49:09 UTC
Parallelism
68/100
Blocked
60%
Avg conflicts / tx
1.16
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,022,436 · 25 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
1w02w13w24w05w16w27w08w19w211w013w114w215w318w319w420w122w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3380fadc…cc76
0x34b655…2a6f
8 touches
6 conflicts
0x5d4a7696…13d9
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0xd18a8dca…4530
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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
6 conflicts on slot 0x3380fadcc9…08cc76
Audit this contract →
← previous block·next block →recent activity