← previous blocknext block →recent activity
Analyzing
Block #101,086,610
39 transactions · 32 stateful · 2026-09-01 16:12:20 UTC
Parallelism
92/100
Blocked
22%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,086,610 · 39 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
1w04w05w16w07w110w011w120w123w235w037w138w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xac33ff75…077b
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x0705cc6c…2c40
0x851145…3f07
4 touches
1 conflict
0xea5af341…ad06
0x851145…3f07
4 touches
1 conflict
0x00000000…0000
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…0001
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity