Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5adf12f033abd3b9d03007adf18d72c567900f8a3f4970db1c69e8bbe8fa0ea8

Tx prefix hash: b809ee04dcacf0537707ae49f86c952361e79eadad08770e47aec36d9e7b075e
Tx public key: 0858d80aec05aa32c383fcdc094ece3b6b857eaab9f25aa4f27826eb1300cf67
Timestamp: 1733753711 Timestamp [UCT]: 2024-12-09 14:15:11 Age [y:d:h:m:s]: 00:191:02:13:43
Block: 1171484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136284 RingCT/type: yes/0
Extra: 010858d80aec05aa32c383fcdc094ece3b6b857eaab9f25aa4f27826eb1300cf670211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c45883d93ca6d70a05ad1b20a3c3d7fbc27956ca252f84f1b6ccc63d25b5b30 0.600000000000 1657247 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": 1171494, "vin": [ { "gen": { "height": 1171484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c45883d93ca6d70a05ad1b20a3c3d7fbc27956ca252f84f1b6ccc63d25b5b30" } } ], "extra": [ 1, 8, 88, 216, 10, 236, 5, 170, 50, 195, 131, 252, 220, 9, 78, 206, 59, 107, 133, 126, 170, 185, 242, 90, 164, 242, 120, 38, 235, 19, 0, 207, 103, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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