← previous blocknext block →recent activity
Analyzing
Block #100,136,012
14 transactions · 13 stateful · 2026-08-29 08:25:13 UTC
Parallelism
64/100
Blocked
54%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,136,012 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w07w28w39w411w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…0003
0xf5b5f7…6d70
6 touches
3 conflicts
0x2fad1943…3586
0x754704…b603
6 touches
3 conflicts
0x69c8bf4a…2ed0
0x754704…b603
6 touches
3 conflicts
0x6a07d677…54ca
0x754704…b603
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x00000000…0007
0xc35b1c…298f
6 touches
3 conflicts
0x00000000…000a
0xc35b1c…298f
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 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity