← previous blocknext block →recent activity
Analyzing
Block #101,656,635
25 transactions · 23 stateful · 2026-09-03 16:00:13 UTC
Parallelism
68/100
Blocked
61%
Avg conflicts / tx
1.6
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,656,635 · 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
1w03w07w08w19w210w312w213w314w416w417w118w520w324w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9430e759…86df
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xcb45d9d6…cb84
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0x72f84659…7466
0xd32edf…ff58
7 touches
6 conflicts
0x7de57974…f5ba
0x34b655…2a6f
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
15 conflicts on slot 0x9430e759ab…3f86df
Audit this contract →
← previous block·next block →recent activity