Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc91f24712c94f84858d99a22a1c847f4c66ff28538e5f2f1de7b2a1606c1cc5

Tx prefix hash: bf3b324bc54aade59842f9a8390b4b59fb73d86fdf706fa96f8e1e29b094246a
Tx public key: a87d3bfb3581552e20b8925c90f4b09f08bcb09fa5129be679efacf289256c82
Timestamp: 1754387970 Timestamp [UCT]: 2025-08-05 09:59:30 Age [y:d:h:m:s]: 00:016:08:27:33
Block: 1340709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10738 RingCT/type: yes/0
Extra: 01a87d3bfb3581552e20b8925c90f4b09f08bcb09fa5129be679efacf289256c820211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db2e4580f7e535560c823d03aa81b4d9b1a2508f235c030308a58e5ddf4aa0f0 0.600000000000 1828528 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": 1340719, "vin": [ { "gen": { "height": 1340709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db2e4580f7e535560c823d03aa81b4d9b1a2508f235c030308a58e5ddf4aa0f0" } } ], "extra": [ 1, 168, 125, 59, 251, 53, 129, 85, 46, 32, 184, 146, 92, 144, 244, 176, 159, 8, 188, 176, 159, 165, 18, 155, 230, 121, 239, 172, 242, 137, 37, 108, 130, 2, 17, 0, 0, 0, 2, 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