Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 721569ab5c5443ecdd9c7227790a2720ef5bec142cc51aeb9ee862e4ef50b49a

Tx prefix hash: 1a8a465b16db8308b2bc8cd61bc922558e52a17c2fbf49097af92b3aa6de76c4
Tx public key: 3c4f8ef9ba6287d74f287eb47d921ad24d533ae9e128a25f6409b2867e5e97c4
Timestamp: 1712288867 Timestamp [UCT]: 2024-04-05 03:47:47 Age [y:d:h:m:s]: 00:285:04:08:22
Block: 993593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204153 RingCT/type: yes/0
Extra: 013c4f8ef9ba6287d74f287eb47d921ad24d533ae9e128a25f6409b2867e5e97c40211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3a2ce6300ca5f609d5ef5e0260d021755b4b049e95dda1173ca785319fa5e81 0.600000000000 1453979 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": 993603, "vin": [ { "gen": { "height": 993593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3a2ce6300ca5f609d5ef5e0260d021755b4b049e95dda1173ca785319fa5e81" } } ], "extra": [ 1, 60, 79, 142, 249, 186, 98, 135, 215, 79, 40, 126, 180, 125, 146, 26, 210, 77, 83, 58, 233, 225, 40, 162, 95, 100, 9, 178, 134, 126, 94, 151, 196, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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