Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a0baa2c830932f7baf3a3c6b460deba809338ef537bee41bd21d2d37f283946

Tx prefix hash: d6480a65690eee4bd0a734208cf320dbed936440a0cced8386ea625b5bfa5d79
Tx public key: e5adec8c9da163fd60d0b9f5f584fba61e80d138ccd76d5b89718a9d98e05143
Timestamp: 1763398363 Timestamp [UCT]: 2025-11-17 16:52:43 Age [y:d:h:m:s]: 00:009:16:01:41
Block: 1414219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6932 RingCT/type: yes/0
Extra: 01e5adec8c9da163fd60d0b9f5f584fba61e80d138ccd76d5b89718a9d98e0514302110000000117b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 080f34fd5a909431fc45564591b765ee62fdbd419c431e36e3f7a6aca7ae724b 0.600000000000 1902706 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": 1414229, "vin": [ { "gen": { "height": 1414219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "080f34fd5a909431fc45564591b765ee62fdbd419c431e36e3f7a6aca7ae724b" } } ], "extra": [ 1, 229, 173, 236, 140, 157, 161, 99, 253, 96, 208, 185, 245, 245, 132, 251, 166, 30, 128, 209, 56, 204, 215, 109, 91, 137, 113, 138, 157, 152, 224, 81, 67, 2, 17, 0, 0, 0, 1, 23, 177, 145, 50, 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