Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e68c769eb2bf31dda329fee298690b593829bddfc2bcf585bdea8c93c9d484bc

Tx prefix hash: 468e5b317a7e40c75ae9947c49d46f1a2adac322f87c211ce5561bb2cdbed366
Tx public key: aab535dd1ead6b2b243afb251d97bde5e98aec16c6843672c40244d0d6156eb8
Timestamp: 1756344911 Timestamp [UCT]: 2025-08-28 01:35:11 Age [y:d:h:m:s]: 00:085:21:47:46
Block: 1355955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61319 RingCT/type: yes/0
Extra: 01aab535dd1ead6b2b243afb251d97bde5e98aec16c6843672c40244d0d6156eb80211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42f40757e89431c9b1bb5582afb6b3895b49037c42f978ddb38ccf5343de9ab9 0.600000000000 1843960 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": 1355965, "vin": [ { "gen": { "height": 1355955 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42f40757e89431c9b1bb5582afb6b3895b49037c42f978ddb38ccf5343de9ab9" } } ], "extra": [ 1, 170, 181, 53, 221, 30, 173, 107, 43, 36, 58, 251, 37, 29, 151, 189, 229, 233, 138, 236, 22, 198, 132, 54, 114, 196, 2, 68, 208, 214, 21, 110, 184, 2, 17, 0, 0, 0, 1, 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