Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee69cd235d4ff1b3c0af3b75d22dbde9b9539e721d45f1365d39bab3f6eddfc7

Tx prefix hash: 19f246737ee99f239c81404ee41d05bb2c2fffac6ea9c7b02d103be081eeaed4
Tx public key: 865b6e49c610289a72909876e13e7a72f99590b7f2bf43a977e8b63843fcdeb4
Timestamp: 1714381197 Timestamp [UCT]: 2024-04-29 08:59:57 Age [y:d:h:m:s]: 00:357:21:01:44
Block: 1010969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255834 RingCT/type: yes/0
Extra: 01865b6e49c610289a72909876e13e7a72f99590b7f2bf43a977e8b63843fcdeb40211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1cc748f9c1eb798511d9188ec91fff2179e26b14b7439a01cb1a832dda8a045 0.600000000000 1473067 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": 1010979, "vin": [ { "gen": { "height": 1010969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1cc748f9c1eb798511d9188ec91fff2179e26b14b7439a01cb1a832dda8a045" } } ], "extra": [ 1, 134, 91, 110, 73, 198, 16, 40, 154, 114, 144, 152, 118, 225, 62, 122, 114, 249, 149, 144, 183, 242, 191, 67, 169, 119, 232, 182, 56, 67, 252, 222, 180, 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