Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c685a7e25b45b25edb7436c3b74d48e2d463dfb84475232a21d0d69e8e7a6705

Tx prefix hash: 9fb79ee429713634c9f25444f19c5e9975de4c037cfe70a4da15ff59f8f31f0a
Tx public key: f975929b762f1b3aba329469e157f57c01c77b2b7696e4192d9b6ef429610ff2
Timestamp: 1742905453 Timestamp [UCT]: 2025-03-25 12:24:13 Age [y:d:h:m:s]: 00:255:04:29:34
Block: 1246970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180131 RingCT/type: yes/0
Extra: 01f975929b762f1b3aba329469e157f57c01c77b2b7696e4192d9b6ef429610ff202110000000624ff4ea1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e543c7e57f46682e2fd74eb061761479c213241b3525df82c1e405fcb4e9657 0.600000000000 1733971 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": 1246980, "vin": [ { "gen": { "height": 1246970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e543c7e57f46682e2fd74eb061761479c213241b3525df82c1e405fcb4e9657" } } ], "extra": [ 1, 249, 117, 146, 155, 118, 47, 27, 58, 186, 50, 148, 105, 225, 87, 245, 124, 1, 199, 123, 43, 118, 150, 228, 25, 45, 155, 110, 244, 41, 97, 15, 242, 2, 17, 0, 0, 0, 6, 36, 255, 78, 161, 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