← previous blocknext block →recent activity
Analyzing
Block #100,627,029
24 transactions · 19 stateful · 2026-08-31 01:39:39 UTC
Parallelism
83/100
Blocked
53%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,627,029 · 24 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
2w03w14w15w26w38w210w011w112w014w015w116w117w218w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x0b104f98…d9ee
0xc8689a…ee79
6 touches
3 conflicts
0xabde8104…c9a9
0x2a68ba…90c5
6 touches
3 conflicts
0x40970e69…da50
0x34ae4d…3fc5
6 touches
3 conflicts
0x8cf3d245…1d0d
0x34ae4d…3fc5
6 touches
3 conflicts
0xb5c4826d…bdd6
0x34ae4d…3fc5
6 touches
3 conflicts
0xdb067026…9eb8
0x34ae4d…3fc5
6 touches
3 conflicts
0xe566e4e7…af2c
0x34b655…2a6f
6 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
6 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity