Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6d0021147caa94ae14fab8d2a994af7d4566e7b01df59c66f9b8ca272407ae8

Tx prefix hash: aa65137f0fe9b3611756ac77e05ec70ed81adc8dea3130c4698c34dda9fa8d03
Tx public key: c01dcf7dcaeedc7c297e44b55098581773a36dae10fb82e525b4e107b981973a
Timestamp: 1703820716 Timestamp [UCT]: 2023-12-29 03:31:56 Age [y:d:h:m:s]: 01:317:19:50:42
Block: 923419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485984 RingCT/type: yes/0
Extra: 01c01dcf7dcaeedc7c297e44b55098581773a36dae10fb82e525b4e107b981973a021100000003ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c9a5e770e65aa86f7e8723d5a273207e29d37376a9cced4e36434da28c6254c 0.600000000000 1381151 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": 923429, "vin": [ { "gen": { "height": 923419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c9a5e770e65aa86f7e8723d5a273207e29d37376a9cced4e36434da28c6254c" } } ], "extra": [ 1, 192, 29, 207, 125, 202, 238, 220, 124, 41, 126, 68, 181, 80, 152, 88, 23, 115, 163, 109, 174, 16, 251, 130, 229, 37, 180, 225, 7, 185, 129, 151, 58, 2, 17, 0, 0, 0, 3, 173, 86, 148, 172, 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