Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 75a794273d0bc9f08426fda4af304d0c114dcfcf94286747fca35cb96718f480

Tx prefix hash: 68ec1b43077b6013ffa1d0816241e6918eef08daa281b42c8d39ef636e894a99
Tx public key: 241e97f993379612df6b34b86cc3a042e9851e6f9059a7de6f9f20bf0fe49c8c
Timestamp: 1738875493 Timestamp [UCT]: 2025-02-06 20:58:13 Age [y:d:h:m:s]: 00:280:07:47:45
Block: 1213620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198092 RingCT/type: yes/0
Extra: 01241e97f993379612df6b34b86cc3a042e9851e6f9059a7de6f9f20bf0fe49c8c0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3b23114d486f529b78145ecf1de1399dfc167fc963712053a1a5d55d3762f3c 0.600000000000 1700399 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1213630, "vin": [ { "gen": { "height": 1213620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3b23114d486f529b78145ecf1de1399dfc167fc963712053a1a5d55d3762f3c" } } ], "extra": [ 1, 36, 30, 151, 249, 147, 55, 150, 18, 223, 107, 52, 184, 108, 195, 160, 66, 233, 133, 30, 111, 144, 89, 167, 222, 111, 159, 32, 191, 15, 228, 156, 140, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8