Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17494447255f22593455e7c34cddd62d9af6e32ff228f4963639b93cc6b63964

Tx prefix hash: 36c6dffcb84093c960d430d8fd925df71b95989a66f2200df7f7b22f6f3197f8
Tx public key: 75231df57a0ec4c92f0a1bd4cc5755105cefb2b5cda60e66f13f7034e8483859
Timestamp: 1705772647 Timestamp [UCT]: 2024-01-20 17:44:07 Age [y:d:h:m:s]: 01:081:05:05:46
Block: 939573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319149 RingCT/type: yes/0
Extra: 0175231df57a0ec4c92f0a1bd4cc5755105cefb2b5cda60e66f13f7034e848385902110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f1a1013639da9c765fcfdb89dd1e23de781597fcc1c9379e55a7fb42049b900 0.600000000000 1397681 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": 939583, "vin": [ { "gen": { "height": 939573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f1a1013639da9c765fcfdb89dd1e23de781597fcc1c9379e55a7fb42049b900" } } ], "extra": [ 1, 117, 35, 29, 245, 122, 14, 196, 201, 47, 10, 27, 212, 204, 87, 85, 16, 92, 239, 178, 181, 205, 166, 14, 102, 241, 63, 112, 52, 232, 72, 56, 89, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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