← previous blocknext block →recent activity
Analyzing
Block #100,106,379
21 transactions · 16 stateful · 2026-08-29 05:55:54 UTC
Parallelism
81/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,106,379 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w26w38w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x33cebe22…672e
0x065c9d…c394
3 touches
1 conflict
0x61c76821…085c
0x40c49f…2af0
3 touches
1 conflict
0x6767cc01…d6eb
0x065c9d…c394
3 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
2 touches
0 conflicts
0x09beabbc…065c
0x188d58…ea8e
2 touches
0 conflicts
0x09beabbc…065d
0x188d58…ea8e
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
6 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity