Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efdf0e8bf8f1f7292648da4f2ef124eadd01de4365346ae88b1ee0af3d8c96bb

Tx prefix hash: 2cd2c072b702746448a7dd9f56bddb7fcdacb5378dfc62552cf9d1099edf00c6
Tx public key: 1d6f670bc9fff2387041275e5a105c10667f6d4a1d24eb51ff3d0fc231501d27
Timestamp: 1703947319 Timestamp [UCT]: 2023-12-30 14:41:59 Age [y:d:h:m:s]: 01:057:11:57:34
Block: 924484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302147 RingCT/type: yes/0
Extra: 011d6f670bc9fff2387041275e5a105c10667f6d4a1d24eb51ff3d0fc231501d270211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd39c63bcc8634361ee9dce3f938556af4158b59d1e66e183861e056f11b50e3 0.600000000000 1382236 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": 924494, "vin": [ { "gen": { "height": 924484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd39c63bcc8634361ee9dce3f938556af4158b59d1e66e183861e056f11b50e3" } } ], "extra": [ 1, 29, 111, 103, 11, 201, 255, 242, 56, 112, 65, 39, 94, 90, 16, 92, 16, 102, 127, 109, 74, 29, 36, 235, 81, 255, 61, 15, 194, 49, 80, 29, 39, 2, 17, 0, 0, 0, 2, 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