Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65312d6f1f22c6aa9e1b1cdd0cdad7dbbec9135e6726eb1a8ce862c6566e1733

Tx prefix hash: 4d199d3345f4b3d90225559f91bd5eb364780139822a2980f4a889cc7ffdb7c9
Tx public key: 57d7f76dca796d82831d02fc668eab7f3e7fb90017f5da740c814596bb6aed31
Timestamp: 1705743944 Timestamp [UCT]: 2024-01-20 09:45:44 Age [y:d:h:m:s]: 01:003:23:41:50
Block: 939333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264140 RingCT/type: yes/0
Extra: 0157d7f76dca796d82831d02fc668eab7f3e7fb90017f5da740c814596bb6aed310211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b5d2042098f9f9e1793cbb3f33c61e76aa2a2a2055f3ebf4525e5c9c14cda3b 0.600000000000 1397427 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": 939343, "vin": [ { "gen": { "height": 939333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b5d2042098f9f9e1793cbb3f33c61e76aa2a2a2055f3ebf4525e5c9c14cda3b" } } ], "extra": [ 1, 87, 215, 247, 109, 202, 121, 109, 130, 131, 29, 2, 252, 102, 142, 171, 127, 62, 127, 185, 0, 23, 245, 218, 116, 12, 129, 69, 150, 187, 106, 237, 49, 2, 17, 0, 0, 0, 3, 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