Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 175ffc56c9e37d89d8294ea96e25ee8d85cb749ab7ecf6b8755acf2253cd5995

Tx prefix hash: 4ff1b3515010bcdcebf072bd9597569518d5ffb0263fab042ec5e5c956b2b97e
Tx public key: 054cd3acb8858df3c34de0b3aa536ae4ee825ae25defa7dfb0635e537d10a295
Timestamp: 1650712271 Timestamp [UCT]: 2022-04-23 11:11:11 Age [y:d:h:m:s]: 02:245:09:23:16
Block: 486349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 695366 RingCT/type: yes/0
Extra: 01054cd3acb8858df3c34de0b3aa536ae4ee825ae25defa7dfb0635e537d10a29502110000000ebf7ee4e7000000000000000000

1 output(s) for total of 15.014957091000 dcy

stealth address amount amount idx
00: 3a10095c990afd1f4566c3396c7c8e9d4d3281f4a236f0b0ea96d323c61c72c0 15.014957091000 908616 of 0

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": 486359, "vin": [ { "gen": { "height": 486349 } } ], "vout": [ { "amount": 15014957091, "target": { "key": "3a10095c990afd1f4566c3396c7c8e9d4d3281f4a236f0b0ea96d323c61c72c0" } } ], "extra": [ 1, 5, 76, 211, 172, 184, 133, 141, 243, 195, 77, 224, 179, 170, 83, 106, 228, 238, 130, 90, 226, 93, 239, 167, 223, 176, 99, 94, 83, 125, 16, 162, 149, 2, 17, 0, 0, 0, 14, 191, 126, 228, 231, 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