Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e47a7dc8a427e8ccfe984de597ad7f6cd8bb0ef1576bff633fc07e19094b21af

Tx prefix hash: 8afc9c4dd92d5ab757b869e4e3f074aa014744bda565fdff89aea0ef136c9387
Tx public key: c9cf471c3a387fa8b0a68287e7827f31fdbeeec4ff7847818c5f8e9da798e9ce
Timestamp: 1721221822 Timestamp [UCT]: 2024-07-17 13:10:22 Age [y:d:h:m:s]: 00:258:01:05:50
Block: 1067699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184324 RingCT/type: yes/0
Extra: 01c9cf471c3a387fa8b0a68287e7827f31fdbeeec4ff7847818c5f8e9da798e9ce02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18aa3edd69224acafa70d7c985a4a668396f08d1c26668832a815057adf5dd88 0.600000000000 1538582 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": 1067709, "vin": [ { "gen": { "height": 1067699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18aa3edd69224acafa70d7c985a4a668396f08d1c26668832a815057adf5dd88" } } ], "extra": [ 1, 201, 207, 71, 28, 58, 56, 127, 168, 176, 166, 130, 135, 231, 130, 127, 49, 253, 190, 238, 196, 255, 120, 71, 129, 140, 95, 142, 157, 167, 152, 233, 206, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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