Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d041ac7ef8b83f19ee5b0dd1897b0346bc4c5c64088ad2950600624ef9c94c7c

Tx prefix hash: 4aebd611ce819fff4535307ff4853e3db2b0130192d2a0955abf660f3b00d14e
Tx public key: 9e021a196e0d8df19ae06ef39e8e64e69914c814581c22ae834bf3aceb94070a
Timestamp: 1737675781 Timestamp [UCT]: 2025-01-23 23:43:01 Age [y:d:h:m:s]: 00:298:06:38:09
Block: 1203900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210722 RingCT/type: yes/0
Extra: 019e021a196e0d8df19ae06ef39e8e64e69914c814581c22ae834bf3aceb94070a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc344e02203e34af6e56eba255bffd4f3a6266674bd37014c8d92ca60bd71c14 0.600000000000 1690581 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": 1203910, "vin": [ { "gen": { "height": 1203900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc344e02203e34af6e56eba255bffd4f3a6266674bd37014c8d92ca60bd71c14" } } ], "extra": [ 1, 158, 2, 26, 25, 110, 13, 141, 241, 154, 224, 110, 243, 158, 142, 100, 230, 153, 20, 200, 20, 88, 28, 34, 174, 131, 75, 243, 172, 235, 148, 7, 10, 2, 17, 0, 0, 0, 2, 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