← previous blocknext block →recent activity
Analyzing
Block #100,922,051
11 transactions · 11 stateful · 2026-09-01 02:24:06 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,922,051 · 11 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
2w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22592be5…7eea
0x065c9d…c394
7 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
6 touches
3 conflicts
0x035f11ba…07e7
0x0898c3…f274
2 touches
0 conflicts
0x899a0e35…c279
0x0898c3…f274
2 touches
0 conflicts
0xdb1960a0…7eb8
0x0898c3…f274
2 touches
0 conflicts
0x00000000…0008
0x5aff25…7440
2 touches
0 conflicts
0x0e54d235…ba7c
0x5e49e1…2e0e
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: Market-MON/USDC
6 conflicts on slot 0x22592be5a4…9d7eea
Audit this contract →
← previous block·next block →recent activity