Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2785edc34419f262dd45e3560be2b43fb688b859e398586e79fa20380beb35db

Tx prefix hash: 9ef56bc2d7ddfd8ab60f8dfe08670fb01f9a908d86046e6b7799cb65861a1190
Tx public key: f2dd540e00cdaef52a9cd959417d894427a9da3d28d28b134009bfa4f6fc11e8
Timestamp: 1752897666 Timestamp [UCT]: 2025-07-19 04:01:06 Age [y:d:h:m:s]: 00:115:09:28:40
Block: 1328575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81252 RingCT/type: yes/0
Extra: 01f2dd540e00cdaef52a9cd959417d894427a9da3d28d28b134009bfa4f6fc11e80211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e9ecf69dfd94566c26fb5b710fec4a542e3a25c9dafc21d6c32985b8dfc3d4d 0.600000000000 1816338 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": 1328585, "vin": [ { "gen": { "height": 1328575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e9ecf69dfd94566c26fb5b710fec4a542e3a25c9dafc21d6c32985b8dfc3d4d" } } ], "extra": [ 1, 242, 221, 84, 14, 0, 205, 174, 245, 42, 156, 217, 89, 65, 125, 137, 68, 39, 169, 218, 61, 40, 210, 139, 19, 64, 9, 191, 164, 246, 252, 17, 232, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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