Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f855cd92132615a933aa50218f5cfa71f45d82c72c153ed40ef3235762d1d4ed

Tx prefix hash: 4e1ed1ede19e7c30fd537f73228dcffb7faef884b5946b2c53cf0bd38687fc62
Tx public key: f3513f27c3a4a4642e4b46956fc9c4d28da5967fe0a61e0f17e8032b1f303476
Timestamp: 1720364682 Timestamp [UCT]: 2024-07-07 15:04:42 Age [y:d:h:m:s]: 00:270:03:38:16
Block: 1060573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193014 RingCT/type: yes/0
Extra: 01f3513f27c3a4a4642e4b46956fc9c4d28da5967fe0a61e0f17e8032b1f3034760211000000038fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7023067de9af20b4e2c091b36c768286e909a7df63661a42692f89f337132cc5 0.600000000000 1531058 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": 1060583, "vin": [ { "gen": { "height": 1060573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7023067de9af20b4e2c091b36c768286e909a7df63661a42692f89f337132cc5" } } ], "extra": [ 1, 243, 81, 63, 39, 195, 164, 164, 100, 46, 75, 70, 149, 111, 201, 196, 210, 141, 165, 150, 127, 224, 166, 30, 15, 23, 232, 3, 43, 31, 48, 52, 118, 2, 17, 0, 0, 0, 3, 143, 218, 155, 45, 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