Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ceb73fc1b202117a80136c0594a275eaa8ead6162a92c5f0cad584b0eb2dc8f

Tx prefix hash: 59ae20bd801c3553374ac9b9f49e9844c051cd1dbfd228121d50dc6c0af37869
Tx public key: 57fadb1876ea29d4d6295a5e5608fd7a3899ab1a455f8703625fbe6cccdf5a07
Timestamp: 1732065737 Timestamp [UCT]: 2024-11-20 01:22:17 Age [y:d:h:m:s]: 00:004:05:08:57
Block: 1157498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3003 RingCT/type: yes/0
Extra: 0157fadb1876ea29d4d6295a5e5608fd7a3899ab1a455f8703625fbe6cccdf5a07021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a692153a5081b662fdf9b0aa468dbad61bcd110cc99f270d0ab8cf386cbb7f6e 0.600000000000 1643121 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": 1157508, "vin": [ { "gen": { "height": 1157498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a692153a5081b662fdf9b0aa468dbad61bcd110cc99f270d0ab8cf386cbb7f6e" } } ], "extra": [ 1, 87, 250, 219, 24, 118, 234, 41, 212, 214, 41, 90, 94, 86, 8, 253, 122, 56, 153, 171, 26, 69, 95, 135, 3, 98, 95, 190, 108, 204, 223, 90, 7, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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