Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16cd1978a2e6ede1d926098b7d96eefcaa70bad2c3adb4cef1d189657e209e23

Tx prefix hash: 8483bbb249c4732c9f4adbc52f1b773acde39e397ed442a72e0e7e03293841c9
Tx public key: 8d7937d0d9f9e9d78a283de20505c595904bc49adfec968e251c7e9a14ac33ff
Timestamp: 1736939921 Timestamp [UCT]: 2025-01-15 11:18:41 Age [y:d:h:m:s]: 00:154:06:49:52
Block: 1197839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109979 RingCT/type: yes/0
Extra: 018d7937d0d9f9e9d78a283de20505c595904bc49adfec968e251c7e9a14ac33ff021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a4ce85d3e6a19a8c45d515f4449d4709c5e137ac9755d30798cd20f23bd9a49 0.600000000000 1684456 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": 1197849, "vin": [ { "gen": { "height": 1197839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a4ce85d3e6a19a8c45d515f4449d4709c5e137ac9755d30798cd20f23bd9a49" } } ], "extra": [ 1, 141, 121, 55, 208, 217, 249, 233, 215, 138, 40, 61, 226, 5, 5, 197, 149, 144, 75, 196, 154, 223, 236, 150, 142, 37, 28, 126, 154, 20, 172, 51, 255, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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