Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95b07fb39e1b34d663e5f6db7d61889ae5ddf27d37576c021aef1ed1d31b5acc

Tx prefix hash: 578baad64bb488f644fb3a3ace6ce61ce419a69d753a90cc893caad330338a40
Tx public key: 19f32a1ea71a99f3968589de3506a71c9b8ef198f28de22aa771e7a14d471ec4
Timestamp: 1749287644 Timestamp [UCT]: 2025-06-07 09:14:04 Age [y:d:h:m:s]: 00:166:11:08:32
Block: 1299815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116652 RingCT/type: yes/0
Extra: 0119f32a1ea71a99f3968589de3506a71c9b8ef198f28de22aa771e7a14d471ec4021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5f9a9665c652b331cf46f12ad324c4af60c709d2acf3f73ece4f110d52cc746 0.600000000000 1787354 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": 1299825, "vin": [ { "gen": { "height": 1299815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5f9a9665c652b331cf46f12ad324c4af60c709d2acf3f73ece4f110d52cc746" } } ], "extra": [ 1, 25, 243, 42, 30, 167, 26, 153, 243, 150, 133, 137, 222, 53, 6, 167, 28, 155, 142, 241, 152, 242, 141, 226, 42, 167, 113, 231, 161, 77, 71, 30, 196, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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