Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa5757960f1b87739d126a844aa36e5526e66ff6b34020d5e1ee2489bf954aa1

Tx prefix hash: 3867cd140b7375f41c1e86964c3994b9e98d14e03d8031865d3b95ae61d177eb
Tx public key: 4e7cfb2b6d3a650b57430d56ffdc4cae686896a6b509e5f442c4407f28309461
Timestamp: 1712722284 Timestamp [UCT]: 2024-04-10 04:11:24 Age [y:d:h:m:s]: 01:224:02:51:41
Block: 997198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418873 RingCT/type: yes/0
Extra: 014e7cfb2b6d3a650b57430d56ffdc4cae686896a6b509e5f442c4407f2830946102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e54031823307852807a29de005419575bcdfbb97d526d80e51af36bbf1b3cb6e 0.600000000000 1457628 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": 997208, "vin": [ { "gen": { "height": 997198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e54031823307852807a29de005419575bcdfbb97d526d80e51af36bbf1b3cb6e" } } ], "extra": [ 1, 78, 124, 251, 43, 109, 58, 101, 11, 87, 67, 13, 86, 255, 220, 76, 174, 104, 104, 150, 166, 181, 9, 229, 244, 66, 196, 64, 127, 40, 48, 148, 97, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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