Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64e5d3a0dd471e48237fe4264c8ab481c1dcd1d948608926aa27882b41a4efd8

Tx prefix hash: 2d276e66aaa26017e93119f8cd813deddb25c1400d46993c118bd4f3c0dd70a7
Tx public key: df8c685174fd373e0cbc504fcaa63feccd36f4b8b98d5325adb3b42ff45c7f1b
Timestamp: 1709965418 Timestamp [UCT]: 2024-03-09 06:23:38 Age [y:d:h:m:s]: 01:246:16:55:12
Block: 974375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435026 RingCT/type: yes/0
Extra: 01df8c685174fd373e0cbc504fcaa63feccd36f4b8b98d5325adb3b42ff45c7f1b02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0685de07ecfa18709053a650a6044b96d81cbe7baef6d0917b02a287dca9c206 0.600000000000 1434330 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": 974385, "vin": [ { "gen": { "height": 974375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0685de07ecfa18709053a650a6044b96d81cbe7baef6d0917b02a287dca9c206" } } ], "extra": [ 1, 223, 140, 104, 81, 116, 253, 55, 62, 12, 188, 80, 79, 202, 166, 63, 236, 205, 54, 244, 184, 185, 141, 83, 37, 173, 179, 180, 47, 244, 92, 127, 27, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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