Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa7d27f09caa1c5c8b9170c9f4e1fdd8e4c9458a268b0ae95e04071855dd2230

Tx prefix hash: c46750a431bdeac65792dd7d00ecb0b94b031f892aff398d60986a1e347bef51
Tx public key: 643541b77cc7a3d1c54c975436acede2a115690993a33dac50f0810d78682f85
Timestamp: 1713713524 Timestamp [UCT]: 2024-04-21 15:32:04 Age [y:d:h:m:s]: 00:328:18:14:10
Block: 1005431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235041 RingCT/type: yes/0
Extra: 01643541b77cc7a3d1c54c975436acede2a115690993a33dac50f0810d78682f850211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17f33aa9f6a4fc5ce3cf798eb6c7e05537fb791cfc84ef27e8e8bab3014aec0b 0.600000000000 1466115 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": 1005441, "vin": [ { "gen": { "height": 1005431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17f33aa9f6a4fc5ce3cf798eb6c7e05537fb791cfc84ef27e8e8bab3014aec0b" } } ], "extra": [ 1, 100, 53, 65, 183, 124, 199, 163, 209, 197, 76, 151, 84, 54, 172, 237, 226, 161, 21, 105, 9, 147, 163, 61, 172, 80, 240, 129, 13, 120, 104, 47, 133, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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