← previous blocknext block →recent activity
Analyzing
Block #101,092,868
27 transactions · 18 stateful · 2026-09-01 16:43:49 UTC
Parallelism
78/100
Blocked
39%
Avg conflicts / tx
0.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,092,868 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w16w111w215w316w018w419w121w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xdfa159d0…1576
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x29f11e6c…3782
0x065c9d…c394
5 touches
3 conflicts
0x09beabbc…065d
0x188d58…ea8e
4 touches
1 conflict
0x46cb45de…a566
0x188d58…ea8e
4 touches
1 conflict
0x46cb45de…a567
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
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
6 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity