← previous blocknext block →recent activity
Analyzing
Block #101,150,983
79 transactions · 56 stateful · 2026-09-01 21:36:10 UTC
Parallelism
91/100
Blocked
55%
Avg conflicts / tx
1.08
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,150,983 · 79 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
3w04w05w06w17w28w310w422w128w143w545w654w555w159w163w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
14 touches
21 conflicts
0x2aa89618…9977
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x45f562b2…9294
0x34ae4d…3fc5
10 touches
10 conflicts
0x8488f10f…9353
0x34ae4d…3fc5
10 touches
10 conflicts
0x8488f10f…9354
0x34ae4d…3fc5
10 touches
10 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
10 touches
10 conflicts
0xc20bd100…8b0e
0x34ae4d…3fc5
10 touches
10 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: Kuru Exchange: MarginAccount
21 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity