← previous blocknext block →recent activity
Analyzing
Block #100,923,957
30 transactions · 23 stateful · 2026-09-01 02:33:42 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,923,957 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w37w410w013w116w017w118w219w221w122w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0xbe44bf7f…5e9b
0x065c9d…c394
5 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa33f916f…e3ab
0x065c9d…c394
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0xb87af72a…aef6
0x2a68ba…90c5
4 touches
1 conflict
0x48ed1159…abe9
0x34ae4d…3fc5
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
10 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity