Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74ed00c5a9a13f34e704c258552be79c302e7977947fd3b4885dff9520d1ee42

Tx prefix hash: 6cedb2173b520cbc664ef08f0c8c17d4099ba9e4e1de2cc1a5db5d78fc2395d4
Tx public key: 6660af55c169022ef60ea9869d9c56912c212fecc129d3df8a74f2e1670a0218
Timestamp: 1710656205 Timestamp [UCT]: 2024-03-17 06:16:45 Age [y:d:h:m:s]: 01:010:21:07:49
Block: 980117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268722 RingCT/type: yes/0
Extra: 016660af55c169022ef60ea9869d9c56912c212fecc129d3df8a74f2e1670a021802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0b00a65813a030efefaacee9df6bd39c7e75a2d44db2ab8274ef29f8a57243c 0.600000000000 1440176 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": 980127, "vin": [ { "gen": { "height": 980117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0b00a65813a030efefaacee9df6bd39c7e75a2d44db2ab8274ef29f8a57243c" } } ], "extra": [ 1, 102, 96, 175, 85, 193, 105, 2, 46, 246, 14, 169, 134, 157, 156, 86, 145, 44, 33, 47, 236, 193, 41, 211, 223, 138, 116, 242, 225, 103, 10, 2, 24, 2, 17, 0, 0, 0, 1, 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