Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a283d4394d57cc0a41432105782688ed6a6c13b68e7e7aec5535a9adc11e8421

Tx prefix hash: 959f6069860cad6973d686b36777887417469f3c8feaf67e29cf8a4ef2a82ab2
Tx public key: d4e0526d105bb756918d67e259090efecbfc373c8a226de9b529f26334baeb94
Timestamp: 1697348477 Timestamp [UCT]: 2023-10-15 05:41:17 Age [y:d:h:m:s]: 01:177:16:23:43
Block: 869966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388018 RingCT/type: yes/0
Extra: 01d4e0526d105bb756918d67e259090efecbfc373c8a226de9b529f26334baeb9402110000001175e3f0e9000000000000000000

1 output(s) for total of 0.804343449000 dcy

stealth address amount amount idx
00: 2cfaac1f28b64de99a841563a384f634088938ee6b5b06cda229af1e96a5c8ac 0.804343449000 1324831 of 0

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": 869976, "vin": [ { "gen": { "height": 869966 } } ], "vout": [ { "amount": 804343449, "target": { "key": "2cfaac1f28b64de99a841563a384f634088938ee6b5b06cda229af1e96a5c8ac" } } ], "extra": [ 1, 212, 224, 82, 109, 16, 91, 183, 86, 145, 141, 103, 226, 89, 9, 14, 254, 203, 252, 55, 60, 138, 34, 109, 233, 181, 41, 242, 99, 52, 186, 235, 148, 2, 17, 0, 0, 0, 17, 117, 227, 240, 233, 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