← previous blocknext block →recent activity
Analyzing
Block #100,924,380
13 transactions · 9 stateful · 2026-09-01 02:35:49 UTC
Parallelism
85/100
Blocked
22%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,924,380 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x41d69e0d…d7cc
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0a7005b5…7c8c
0x065c9d…c394
2 touches
0 conflicts
0x0c1a0462…e513
0x065c9d…c394
2 touches
0 conflicts
0x41d69e0d…d7cd
0x065c9d…c394
2 touches
0 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
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
1 conflict on slot 0x0778475bb2…63bd75
Audit this contract →
← previous block·next block →recent activity