← previous blocknext block →recent activity
Analyzing
Block #100,920,077
15 transactions · 14 stateful · 2026-09-01 02:14:10 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,920,077 · 15 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
1w05w06w18w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50c3cc97…78f9
0x065c9d…c394
4 touches
1 conflict
0x74e485b1…d380
0x34b655…2a6f
4 touches
1 conflict
0x8b92c0f7…fe33
0x34b655…2a6f
4 touches
1 conflict
0xb00651bd…9600
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x5f77d607…2c84
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8488f10f…9353
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: Market-MON/USDC
1 conflict on slot 0x50c3cc9780…f278f9
Audit this contract →
← previous block·next block →recent activity