Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3670a8c613b9d6d85ad26006cf23daeb7dd8edf4683143fd3986b87325be3a26

Tx prefix hash: 4bb51c86daaf0a8a35335e7e1414d10fb043764ed6cce86f737d0b2dcb984c67
Tx public key: a892255178a00fface7e9d33d0d985b465f02fff44f081b85ee11b8acdcd7f7e
Timestamp: 1712753570 Timestamp [UCT]: 2024-04-10 12:52:50 Age [y:d:h:m:s]: 00:294:16:44:45
Block: 997456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210688 RingCT/type: yes/0
Extra: 01a892255178a00fface7e9d33d0d985b465f02fff44f081b85ee11b8acdcd7f7e0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 583fb5232bf407bcc187469bc766aea6df0760ea64d94aea3be75dde63099549 0.600000000000 1457888 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": 997466, "vin": [ { "gen": { "height": 997456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "583fb5232bf407bcc187469bc766aea6df0760ea64d94aea3be75dde63099549" } } ], "extra": [ 1, 168, 146, 37, 81, 120, 160, 15, 250, 206, 126, 157, 51, 208, 217, 133, 180, 101, 240, 47, 255, 68, 240, 129, 184, 94, 225, 27, 138, 205, 205, 127, 126, 2, 17, 0, 0, 0, 4, 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