Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cb0c304bce97425145e7e48fd503403587bcf7b068be98934e3e1388f168e42

Tx prefix hash: 27126fd121d13c54f60c5d4618d8b3a74f2c5860a74e2c31468bd924b4b88e0c
Tx public key: 766662cb150199626803b08ed3bd5ca1f204863b8e9ff5910fe8ecd1c2e6bfb6
Timestamp: 1760950227 Timestamp [UCT]: 2025-10-20 08:50:27 Age [y:d:h:m:s]: 00:020:13:14:48
Block: 1393958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14699 RingCT/type: yes/0
Extra: 01766662cb150199626803b08ed3bd5ca1f204863b8e9ff5910fe8ecd1c2e6bfb602110000000625a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66b1f6154f586ece19ba2c49b5df889e1f502401d2b75b0fad4afcd5696491cc 0.600000000000 1882225 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": 1393968, "vin": [ { "gen": { "height": 1393958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66b1f6154f586ece19ba2c49b5df889e1f502401d2b75b0fad4afcd5696491cc" } } ], "extra": [ 1, 118, 102, 98, 203, 21, 1, 153, 98, 104, 3, 176, 142, 211, 189, 92, 161, 242, 4, 134, 59, 142, 159, 245, 145, 15, 232, 236, 209, 194, 230, 191, 182, 2, 17, 0, 0, 0, 6, 37, 163, 90, 15, 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