Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d3235ba8d25a81458823620e11e6f289bfb2ebd2af827dc71bd84278a4cc466

Tx prefix hash: aae5033df0dc446e1e429e5cfc1c6a23dd9730716f52fe9fa9cab2f57a8422b3
Tx public key: 6d842b4ace74d33efea5509a26104c24d19ff1e32453a515c2e08b57106c0c02
Timestamp: 1719150766 Timestamp [UCT]: 2024-06-23 13:52:46 Age [y:d:h:m:s]: 00:284:11:56:46
Block: 1050497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203298 RingCT/type: yes/0
Extra: 016d842b4ace74d33efea5509a26104c24d19ff1e32453a515c2e08b57106c0c020211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c38d480da6401709803e54455aed17dab3cb2ec8f2cc88620dbdeaa04f5f9aa 0.600000000000 1520670 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": 1050507, "vin": [ { "gen": { "height": 1050497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c38d480da6401709803e54455aed17dab3cb2ec8f2cc88620dbdeaa04f5f9aa" } } ], "extra": [ 1, 109, 132, 43, 74, 206, 116, 211, 62, 254, 165, 80, 154, 38, 16, 76, 36, 209, 159, 241, 227, 36, 83, 165, 21, 194, 224, 139, 87, 16, 108, 12, 2, 2, 17, 0, 0, 0, 1, 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