Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb5b6b6d4651c40deba1f1fcaa0fddd6d551d9dd18c9683601cc5ba3b9759182

Tx prefix hash: 4c2ad196b6d7299fe711472a4ed9ca7a2ce06bb4ab70ffe60f2f4c3c7722cc2a
Tx public key: 17c39617692d4d3cba37402c4850f89125147c89536450abf95078b2938a4abc
Timestamp: 1714716758 Timestamp [UCT]: 2024-05-03 06:12:38 Age [y:d:h:m:s]: 00:141:07:47:22
Block: 1013766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101222 RingCT/type: yes/0
Extra: 0117c39617692d4d3cba37402c4850f89125147c89536450abf95078b2938a4abc0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1f38accb2a8b1427b4dc382c26f3d233192cc5bbfd36d8eb2ff29917f975e74 0.600000000000 1476669 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": 1013776, "vin": [ { "gen": { "height": 1013766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1f38accb2a8b1427b4dc382c26f3d233192cc5bbfd36d8eb2ff29917f975e74" } } ], "extra": [ 1, 23, 195, 150, 23, 105, 45, 77, 60, 186, 55, 64, 44, 72, 80, 248, 145, 37, 20, 124, 137, 83, 100, 80, 171, 249, 80, 120, 178, 147, 138, 74, 188, 2, 17, 0, 0, 0, 8, 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