Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f145d4ec828c5366d4b3204f4f597b759c5e708aec38abf6859962b1246cec6c

Tx prefix hash: c58307478e235b514dada9f0cbef49b738c3a174e18dd201a73636b35ab3b704
Tx public key: f7a3e03acece7d60e38edd9a3181e0a9ba02519df8c3a32b02a05d7585e83a5d
Timestamp: 1705898064 Timestamp [UCT]: 2024-01-22 04:34:24 Age [y:d:h:m:s]: 01:142:07:56:54
Block: 940604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362840 RingCT/type: yes/0
Extra: 01f7a3e03acece7d60e38edd9a3181e0a9ba02519df8c3a32b02a05d7585e83a5d0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ebd547de50c649380a479375356506e0389bdc10014067adb48214a4adc934b 0.600000000000 1398742 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": 940614, "vin": [ { "gen": { "height": 940604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ebd547de50c649380a479375356506e0389bdc10014067adb48214a4adc934b" } } ], "extra": [ 1, 247, 163, 224, 58, 206, 206, 125, 96, 227, 142, 221, 154, 49, 129, 224, 169, 186, 2, 81, 157, 248, 195, 163, 43, 2, 160, 93, 117, 133, 232, 58, 93, 2, 17, 0, 0, 0, 7, 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