← previous blocknext block →recent activity
Analyzing
Block #100,235,936
25 transactions · 21 stateful · 2026-08-29 16:48:15 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,235,936 · 25 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w08w112w218w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0x931b3a3a…70ff
0x065c9d…c394
4 touches
1 conflict
0xd8eadf13…ebbb
0xd32edf…ff58
3 touches
1 conflict
0x12530975…a089
0x3bd359…433a
2 touches
0 conflicts
0x50951f37…219c
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x453805…c7fd
2 touches
0 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
3 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity