← previous blocknext block →recent activity
Analyzing
Block #101,066,099
70 transactions · 44 stateful · 2026-09-01 14:28:54 UTC
Parallelism
84/100
Blocked
55%
Avg conflicts / tx
1.3
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #101,066,099 · 70 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w16w27w311w412w513w624w741w843w959w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
18 touches
36 conflicts
0x3c37984d…8dd5
0xd32edf…ff58
15 touches
28 conflicts
0xc3357180…1cf3
0x065c9d…c394
11 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
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: Kuru Exchange: MarginAccount
36 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity