← previous blocknext block →recent activity
Analyzing
Block #100,920,445
36 transactions · 33 stateful · 2026-09-01 02:16:01 UTC
Parallelism
86/100
Blocked
24%
Avg conflicts / tx
0.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,920,445 · 36 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w010w011w112w213w314w415w130w134w035w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x457fd28d…9e58
0x065c9d…c394
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x0778475b…bd75
0x2a68ba…90c5
10 touches
10 conflicts
0x7ea1cfdf…81c0
0xa6afd3…d132
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x1db5837f…1264
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x886db264…846e
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0x457fd28d47…849e58
Audit this contract →
← previous block·next block →recent activity