Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e289fa7249879ce9779c6d7cc01ce0bdb8165cbaa4ab2e387927939dbc0d1606

Tx prefix hash: 6095841105f6fe98b45242d498891e59c385ea9ca0bed28a077776390bf12cd2
Tx public key: 649f563773ebdbc4d4ea418252f3f42c1c42ce5387531e7d1f8e6bd05ad82fb1
Timestamp: 1737571298 Timestamp [UCT]: 2025-01-22 18:41:38 Age [y:d:h:m:s]: 00:051:04:39:31
Block: 1203030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36414 RingCT/type: yes/0
Extra: 01649f563773ebdbc4d4ea418252f3f42c1c42ce5387531e7d1f8e6bd05ad82fb10211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc983c954bd1d3e49a936ea88df76b0c0189b6f99ed43a36d465c3c965d42ca1 0.600000000000 1689703 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": 1203040, "vin": [ { "gen": { "height": 1203030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc983c954bd1d3e49a936ea88df76b0c0189b6f99ed43a36d465c3c965d42ca1" } } ], "extra": [ 1, 100, 159, 86, 55, 115, 235, 219, 196, 212, 234, 65, 130, 82, 243, 244, 44, 28, 66, 206, 83, 135, 83, 30, 125, 31, 142, 107, 208, 90, 216, 47, 177, 2, 17, 0, 0, 0, 4, 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