Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 474b4f292d9b9e9d2243b88f96391315bef084dd801ef8a2b91ff39af6219fe0

Tx prefix hash: 3fefb2894327ed1d5ced3ba98402d2f4a6ab12044969be0c38da53afea369db5
Tx public key: 598b8e24efea241b9e20290f883f5117e05d7a603855de95caeee64a185d7da0
Timestamp: 1762547017 Timestamp [UCT]: 2025-11-07 20:23:37 Age [y:d:h:m:s]: 00:046:03:53:44
Block: 1407167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33048 RingCT/type: yes/0
Extra: 01598b8e24efea241b9e20290f883f5117e05d7a603855de95caeee64a185d7da00211000000015dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 293dfd4a23c48ca48c094a4372758c12578855008b5c6547c289dbdd8d2752a9 0.600000000000 1895576 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": 1407177, "vin": [ { "gen": { "height": 1407167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "293dfd4a23c48ca48c094a4372758c12578855008b5c6547c289dbdd8d2752a9" } } ], "extra": [ 1, 89, 139, 142, 36, 239, 234, 36, 27, 158, 32, 41, 15, 136, 63, 81, 23, 224, 93, 122, 96, 56, 85, 222, 149, 202, 238, 230, 74, 24, 93, 125, 160, 2, 17, 0, 0, 0, 1, 93, 251, 190, 42, 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