Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1ee4e02898aeaef1bff582f2836721e019d11350caf11e2cc6d5eecaa43b117

Tx prefix hash: 546e33967e777376fc280abc62972352201ff21798060f9ba827eeedc8a68d8f
Tx public key: d682237b486b56cdcb92e05cf9b18a5258942c8c3c939753b9732e6dc27081b2
Timestamp: 1712747794 Timestamp [UCT]: 2024-04-10 11:16:34 Age [y:d:h:m:s]: 01:048:15:15:30
Block: 997407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295774 RingCT/type: yes/0
Extra: 01d682237b486b56cdcb92e05cf9b18a5258942c8c3c939753b9732e6dc27081b20211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb0c7b02305af852d5985ac79a3f6793c41e4cd2bb09cc9765f0e6ba8ea90303 0.600000000000 1457839 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": 997417, "vin": [ { "gen": { "height": 997407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb0c7b02305af852d5985ac79a3f6793c41e4cd2bb09cc9765f0e6ba8ea90303" } } ], "extra": [ 1, 214, 130, 35, 123, 72, 107, 86, 205, 203, 146, 224, 92, 249, 177, 138, 82, 88, 148, 44, 140, 60, 147, 151, 83, 185, 115, 46, 109, 194, 112, 129, 178, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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