Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bc8e6e1c5556df5a94a63c13e535bc10517664297b31f2647811e7cfb117e56

Tx prefix hash: a59c66ebbb908535d451d271d1e417ea12426fcb891aa4f5349060c9b6eb7d31
Tx public key: cb14c94a73634b9728d2475b8749d66591b866b8ec552e1fcd4d3f60c26f8a52
Timestamp: 1705702334 Timestamp [UCT]: 2024-01-19 22:12:14 Age [y:d:h:m:s]: 01:293:10:33:06
Block: 938989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 468551 RingCT/type: yes/0
Extra: 01cb14c94a73634b9728d2475b8749d66591b866b8ec552e1fcd4d3f60c26f8a520211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9773169f1f277704e8e4a834102401328af9b354f0fa95a81485bd15819a96de 0.600000000000 1397073 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": 938999, "vin": [ { "gen": { "height": 938989 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9773169f1f277704e8e4a834102401328af9b354f0fa95a81485bd15819a96de" } } ], "extra": [ 1, 203, 20, 201, 74, 115, 99, 75, 151, 40, 210, 71, 91, 135, 73, 214, 101, 145, 184, 102, 184, 236, 85, 46, 31, 205, 77, 63, 96, 194, 111, 138, 82, 2, 17, 0, 0, 0, 2, 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