← previous blocknext block →recent activity
Analyzing
Block #100,631,057
18 transactions · 16 stateful · 2026-08-31 01:59:55 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,631,057 · 18 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
1w02w13w04w15w27w011w114w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xa1ac5a56…17d8
0x99c7a7…8bf0
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x110ed75b…7ff2
0x40c49f…2af0
4 touches
1 conflict
0xa080891e…f5b3
0x40c49f…2af0
4 touches
1 conflict
0x49f39582…ccc7
0x754704…b603
4 touches
1 conflict
0xad47b33d…500b
0x754704…b603
4 touches
1 conflict
0xf00d2133…d68e
0x754704…b603
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 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity