Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39d471367b268ffba4b515e0a22489488d3dc5f2c508a6d1349044e18ed67aa0

Tx prefix hash: e40f59ea9b141e952493ab668059c858ec95c119a3e835baa810415ed72fe189
Tx public key: a1e8cd7fd1c0b8a16eb29c73cf5ca235c063297c68c1fb89422a05ba02447565
Timestamp: 1719920100 Timestamp [UCT]: 2024-07-02 11:35:00 Age [y:d:h:m:s]: 00:270:19:15:20
Block: 1056895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193482 RingCT/type: yes/0
Extra: 01a1e8cd7fd1c0b8a16eb29c73cf5ca235c063297c68c1fb89422a05ba024475650211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8fd51dac70e8619b83eb8414917908a2701b6748878e083638878c34d0fd2ba9 0.600000000000 1527324 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": 1056905, "vin": [ { "gen": { "height": 1056895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fd51dac70e8619b83eb8414917908a2701b6748878e083638878c34d0fd2ba9" } } ], "extra": [ 1, 161, 232, 205, 127, 209, 192, 184, 161, 110, 178, 156, 115, 207, 92, 162, 53, 192, 99, 41, 124, 104, 193, 251, 137, 66, 42, 5, 186, 2, 68, 117, 101, 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