Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c9b72954d3c995982188ea70acc2199ca58bb41afd369c43ece645707af6c0f

Tx prefix hash: 2d20360f82739da44f60ce51e17b85e150037cb720e85408053733fa235aa6fd
Tx public key: deaa29c0c7ad8588ea2beab618b4ca74fcd57f8518ad195d59d8c34c0ce6e4c3
Timestamp: 1578239952 Timestamp [UCT]: 2020-01-05 15:59:12 Age [y:d:h:m:s]: 04:362:17:15:17
Block: 39306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148467 RingCT/type: yes/0
Extra: 01deaa29c0c7ad8588ea2beab618b4ca74fcd57f8518ad195d59d8c34c0ce6e4c3021100000027dcee4b4d000000000000000000

1 output(s) for total of 454.748474586000 dcy

stealth address amount amount idx
00: 352d437eab88cfcb9f8fba579cd1e036b08a474dce82e584e1ab83f67b5f971a 454.748474586000 67673 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": 39316, "vin": [ { "gen": { "height": 39306 } } ], "vout": [ { "amount": 454748474586, "target": { "key": "352d437eab88cfcb9f8fba579cd1e036b08a474dce82e584e1ab83f67b5f971a" } } ], "extra": [ 1, 222, 170, 41, 192, 199, 173, 133, 136, 234, 43, 234, 182, 24, 180, 202, 116, 252, 213, 127, 133, 24, 173, 25, 93, 89, 216, 195, 76, 12, 230, 228, 195, 2, 17, 0, 0, 0, 39, 220, 238, 75, 77, 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