Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f092f6955977d4f71b3c31391abf6c2d5516f42ec34df5fb3ff71d286a43013

Tx prefix hash: dc1970577a8b17c41c5e263af9772c07e3a0d2f10f7fe7138aaa8a968f94a773
Tx public key: cd92e63b710f281d0a995c9ccf96e7bb967f002328fca5636974311811033699
Timestamp: 1738441321 Timestamp [UCT]: 2025-02-01 20:22:01 Age [y:d:h:m:s]: 00:290:17:52:11
Block: 1210007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205564 RingCT/type: yes/0
Extra: 01cd92e63b710f281d0a995c9ccf96e7bb967f002328fca5636974311811033699021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7e3a27f04cb6a8c48797720fc474f35dc8e202d9bd36dadfb5e4999e5eeb7fd 0.600000000000 1696754 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": 1210017, "vin": [ { "gen": { "height": 1210007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7e3a27f04cb6a8c48797720fc474f35dc8e202d9bd36dadfb5e4999e5eeb7fd" } } ], "extra": [ 1, 205, 146, 230, 59, 113, 15, 40, 29, 10, 153, 92, 156, 207, 150, 231, 187, 150, 127, 0, 35, 40, 252, 165, 99, 105, 116, 49, 24, 17, 3, 54, 153, 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