← previous blocknext block →recent activity
Analyzing
Block #100,723,731
23 transactions · 21 stateful · 2026-08-31 09:46:06 UTC
Parallelism
61/100
Blocked
57%
Avg conflicts / tx
1.22
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,723,731 · 23 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w28w39w410w511w014w216w117w619w720w821w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x7ea1cfdf…81c0
0xa6afd3…d132
8 touches
6 conflicts
0x3f2100d8…f9b5
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xb0767546…ee45
0xa6afd3…d132
5 touches
3 conflicts
0x61cd447e…49e6
0xa6afd3…d132
5 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 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity