Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8957e02faf72fc2683e3f584d77e32632655d434a62bdd371665c6fda9d80b66

Tx prefix hash: cb7f1adc21966d9d5f9ca1b71c731a7fc68c7a07d5de04aaf4384f1728cdc427
Tx public key: f675f196fc0ae9491d0d7f4a22ad9d3131cf1e2efd2f204fdb65f2bdc1f6e429
Timestamp: 1707430968 Timestamp [UCT]: 2024-02-08 22:22:48 Age [y:d:h:m:s]: 01:055:03:31:18
Block: 953339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300458 RingCT/type: yes/0
Extra: 01f675f196fc0ae9491d0d7f4a22ad9d3131cf1e2efd2f204fdb65f2bdc1f6e42902110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f0161fe7fa0f1d3946eeaedff179923e966e96edb768c4b77ff0bae614fe6f5 0.600000000000 1412533 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": 953349, "vin": [ { "gen": { "height": 953339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f0161fe7fa0f1d3946eeaedff179923e966e96edb768c4b77ff0bae614fe6f5" } } ], "extra": [ 1, 246, 117, 241, 150, 252, 10, 233, 73, 29, 13, 127, 74, 34, 173, 157, 49, 49, 207, 30, 46, 253, 47, 32, 79, 219, 101, 242, 189, 193, 246, 228, 41, 2, 17, 0, 0, 0, 7, 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