Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af393d889e0d157e200c1ba749238578f4fb79ae4b45f40ec66341c78d475c6d

Tx prefix hash: 33d96c381bc7aa97e3388b0e2afa3af6fa1dd3bb3bcec090fdcf6c8ef0c6a1d6
Tx public key: 277e0ea91fe1ef39a7818a598ce98b68edfaadcb2985be95ebfac0af0d6652c9
Timestamp: 1714296545 Timestamp [UCT]: 2024-04-28 09:29:05 Age [y:d:h:m:s]: 00:248:06:08:15
Block: 1010271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177694 RingCT/type: yes/0
Extra: 01277e0ea91fe1ef39a7818a598ce98b68edfaadcb2985be95ebfac0af0d6652c902110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bf077c628bb2d8c34a97d99f0d41553999a09455e0e1adc9bcf563b30105d16 0.600000000000 1472177 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": 1010281, "vin": [ { "gen": { "height": 1010271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bf077c628bb2d8c34a97d99f0d41553999a09455e0e1adc9bcf563b30105d16" } } ], "extra": [ 1, 39, 126, 14, 169, 31, 225, 239, 57, 167, 129, 138, 89, 140, 233, 139, 104, 237, 250, 173, 203, 41, 133, 190, 149, 235, 250, 192, 175, 13, 102, 82, 201, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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