Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 428f7a4daa7ada012c27c1f65a8716681c7586ade7d03b2dacccbf879699e9cb

Tx prefix hash: 27c7aeb410cfb1970021b656994fbcf2ba0feae5b369770a05e42cd76b0c380e
Tx public key: d360a56b62660a280017507ae879e72e49e52fc5b2fa57b2fb0920d1ee9428d4
Timestamp: 1748650615 Timestamp [UCT]: 2025-05-31 00:16:55 Age [y:d:h:m:s]: 00:169:19:11:28
Block: 1294541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119042 RingCT/type: yes/0
Extra: 01d360a56b62660a280017507ae879e72e49e52fc5b2fa57b2fb0920d1ee9428d4021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 510da9a3c2aa5e729b8d319060b514c746a1cb9d98527fe1570692b6a7724a26 0.600000000000 1782036 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": 1294551, "vin": [ { "gen": { "height": 1294541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "510da9a3c2aa5e729b8d319060b514c746a1cb9d98527fe1570692b6a7724a26" } } ], "extra": [ 1, 211, 96, 165, 107, 98, 102, 10, 40, 0, 23, 80, 122, 232, 121, 231, 46, 73, 229, 47, 197, 178, 250, 87, 178, 251, 9, 32, 209, 238, 148, 40, 212, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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