← previous blocknext block →recent activity
Analyzing
Block #100,626,289
8 transactions · 8 stateful · 2026-08-31 01:35:56 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,626,289 · 8 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
2w03w14w27w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x1dedc384…ff57
0x851145…3f07
4 touches
1 conflict
0x2ce5d13f…f8a9
0x851145…3f07
4 touches
1 conflict
0xd9daa50d…0ee0
0x851145…3f07
3 touches
1 conflict
0xabde8104…c9a9
0x2a68ba…90c5
2 touches
0 conflicts
0x06d7243a…2d20
0x34ae4d…3fc5
2 touches
0 conflicts
0x1b60b708…5b4b
0x34ae4d…3fc5
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
3 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity