← previous blocknext block →recent activity
Analyzing
Block #100,849,113
33 transactions · 28 stateful · 2026-08-31 20:17:14 UTC
Parallelism
70/100
Blocked
57%
Avg conflicts / tx
1.18
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,849,113 · 33 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w08w19w210w311w412w518w624w125w530w731w832w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x236edd6d…7b84
0x40c49f…2af0
9 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xe61a3df2…f763
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: Kuru Exchange: MarginAccount
10 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity