← previous blocknext block →recent activity
Analyzing
Block #100,560,078
13 transactions · 12 stateful · 2026-08-30 20:02:52 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,560,078 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b3c29a4…3b6f
0x065c9d…c394
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf655036e…06ad
0x065c9d…c394
3 touches
1 conflict
0x517d0989…a1b6
0x065c9d…c394
3 touches
1 conflict
0x10abefc9…c9bc
0x2b46c0…1669
2 touches
0 conflicts
0x10d80fee…dbda
0x2b46c0…1669
2 touches
0 conflicts
0x2f4b2cf9…4e1e
0x2b46c0…1669
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 0x5b3c29a4b2…aa3b6f
Audit this contract →
← previous block·next block →recent activity