Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cbdb7fe88cbb0d7d56bbdfb245a0d4d78a55e229ee959d9adf5b6c327bf83c1

Tx prefix hash: 472e2148cd2cd6fd2f5b3289531e36ac271cbbd3cdeb1d087e1ff61d2b8e6780
Tx public key: 5839f79985d740bb85bfed18b34b20126871474a36ebdcd13da187b916eb9284
Timestamp: 1582333806 Timestamp [UCT]: 2020-02-22 01:10:06 Age [y:d:h:m:s]: 04:315:18:35:46
Block: 69809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118276 RingCT/type: yes/0
Extra: 015839f79985d740bb85bfed18b34b20126871474a36ebdcd13da187b916eb928402110000000112c4732d000000000000000000

1 output(s) for total of 360.325176357000 dcy

stealth address amount amount idx
00: a33616e70ab88d5746e2165675b1ad381ed5253ad6fe046c79d8e7e3b74a7f0a 360.325176357000 128845 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": 69819, "vin": [ { "gen": { "height": 69809 } } ], "vout": [ { "amount": 360325176357, "target": { "key": "a33616e70ab88d5746e2165675b1ad381ed5253ad6fe046c79d8e7e3b74a7f0a" } } ], "extra": [ 1, 88, 57, 247, 153, 133, 215, 64, 187, 133, 191, 237, 24, 179, 75, 32, 18, 104, 113, 71, 74, 54, 235, 220, 209, 61, 161, 135, 185, 22, 235, 146, 132, 2, 17, 0, 0, 0, 1, 18, 196, 115, 45, 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