Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf83a8e87d6ece7a0458ea918611ff839794985e61a3582b6a50e020892ef51c

Tx prefix hash: d865b711a4217b4aaed7763fa85ed24c9f4637b7f48ef2ed54e7de8a6fef8110
Tx public key: 46f196667fa74080d1e3d39801fbb4e6b77dec74e8b72e3ecc2c68a63b533905
Timestamp: 1749668762 Timestamp [UCT]: 2025-06-11 19:06:02 Age [y:d:h:m:s]: 00:163:04:06:13
Block: 1302957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114311 RingCT/type: yes/0
Extra: 0146f196667fa74080d1e3d39801fbb4e6b77dec74e8b72e3ecc2c68a63b5339050211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6310e55aa7d04d86ab7497cfd61d4c2afa442194f4112f6492c06a1e065cda3 0.600000000000 1790532 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": 1302967, "vin": [ { "gen": { "height": 1302957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6310e55aa7d04d86ab7497cfd61d4c2afa442194f4112f6492c06a1e065cda3" } } ], "extra": [ 1, 70, 241, 150, 102, 127, 167, 64, 128, 209, 227, 211, 152, 1, 251, 180, 230, 183, 125, 236, 116, 232, 183, 46, 62, 204, 44, 104, 166, 59, 83, 57, 5, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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