Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3f320e032280a1a954b4a3a40af09f2d924ed9faac8e6d4c219fe5556eee3c8

Tx prefix hash: cd904d7b44eeaa9cedafd7cbf99e0e77acc980d18bb178c29611d8b325bf15ee
Tx public key: a9831499b9b5a01606ad87f6ae541c108ff173c90c02790c98ca926be0265d47
Timestamp: 1720764119 Timestamp [UCT]: 2024-07-12 06:01:59 Age [y:d:h:m:s]: 00:246:09:57:15
Block: 1063901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176044 RingCT/type: yes/0
Extra: 01a9831499b9b5a01606ad87f6ae541c108ff173c90c02790c98ca926be0265d47021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a62cd6e6975ad179640e331419e18de6616cb549503d059c1fb9e01f66260e8 0.600000000000 1534420 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": 1063911, "vin": [ { "gen": { "height": 1063901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a62cd6e6975ad179640e331419e18de6616cb549503d059c1fb9e01f66260e8" } } ], "extra": [ 1, 169, 131, 20, 153, 185, 181, 160, 22, 6, 173, 135, 246, 174, 84, 28, 16, 143, 241, 115, 201, 12, 2, 121, 12, 152, 202, 146, 107, 224, 38, 93, 71, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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