Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9655fc34ee9e60f6c321a975cebeb4b5f0bdd4262b139e1c0732734c99925946

Tx prefix hash: a80b91cc33271e0b96d6944dcaa38b07c8c07248e5fc0f0f87d055513a015dde
Tx public key: d5aacef51c3a8bfe37534419b9e57cfc1f652f5eaf7a5127675a90ae338dc720
Timestamp: 1710768858 Timestamp [UCT]: 2024-03-18 13:34:18 Age [y:d:h:m:s]: 01:001:09:47:53
Block: 981042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261989 RingCT/type: yes/0
Extra: 01d5aacef51c3a8bfe37534419b9e57cfc1f652f5eaf7a5127675a90ae338dc720021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 737e6d411540baeb51113bbdee5bcbd2a29d5b33e522d28d8528b103aebf0699 0.600000000000 1441127 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": 981052, "vin": [ { "gen": { "height": 981042 } } ], "vout": [ { "amount": 600000000, "target": { "key": "737e6d411540baeb51113bbdee5bcbd2a29d5b33e522d28d8528b103aebf0699" } } ], "extra": [ 1, 213, 170, 206, 245, 28, 58, 139, 254, 55, 83, 68, 25, 185, 229, 124, 252, 31, 101, 47, 94, 175, 122, 81, 39, 103, 90, 144, 174, 51, 141, 199, 32, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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