Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19b483fb989b517b2410790e481b5ff47c6ffcca0d183f31a00c1f280a5405dd

Tx prefix hash: 1a8b71f3f83ca3ac442cbd0bda015891b4409ab0acad35875c1824591a4b8e70
Tx public key: 0dbae60f768e5b817b07db398b0af3dcb60c3ceb192b10389f19f1c313b16fc4
Timestamp: 1718922873 Timestamp [UCT]: 2024-06-20 22:34:33 Age [y:d:h:m:s]: 00:278:05:37:53
Block: 1048621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198805 RingCT/type: yes/0
Extra: 010dbae60f768e5b817b07db398b0af3dcb60c3ceb192b10389f19f1c313b16fc40211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d404dd1713f85f8602b682e039b214af68621ea5fa83ebb67941c55407b2ba8d 0.600000000000 1518706 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": 1048631, "vin": [ { "gen": { "height": 1048621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d404dd1713f85f8602b682e039b214af68621ea5fa83ebb67941c55407b2ba8d" } } ], "extra": [ 1, 13, 186, 230, 15, 118, 142, 91, 129, 123, 7, 219, 57, 139, 10, 243, 220, 182, 12, 60, 235, 25, 43, 16, 56, 159, 25, 241, 195, 19, 177, 111, 196, 2, 17, 0, 0, 0, 3, 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