← previous blocknext block →recent activity
Analyzing
Block #104,149,113
11 transactions · 11 stateful · 2026-09-12 09:53:09 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,149,113 · 11 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
1w05w16w07w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0xee4fe1f7…3ead
0x34b655…2a6f
4 touches
1 conflict
0x07e025a5…0279
0x065c9d…c394
2 touches
0 conflicts
0x37806efc…bae1
0x065c9d…c394
2 touches
0 conflicts
0x472d7db9…0465
0x065c9d…c394
2 touches
0 conflicts
0x9d871b94…724a
0x065c9d…c394
2 touches
0 conflicts
0xa75fedfc…21cd
0x065c9d…c394
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity