Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2078f8f532599367717eea916382d713a916e41853d2524d53485231886a7e4

Tx prefix hash: c2be397f510d901a60f39ec363e1790b6d5f3bb7b6aface15ac623b729ada97c
Tx public key: 5e63539e86a4db80f6eba6820d91995100c24447d36e335245d74f6ce62b61e7
Timestamp: 1709063619 Timestamp [UCT]: 2024-02-27 19:53:39 Age [y:d:h:m:s]: 01:282:18:17:59
Block: 966895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460846 RingCT/type: yes/0
Extra: 015e63539e86a4db80f6eba6820d91995100c24447d36e335245d74f6ce62b61e70211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9efb7cd78a2d1d40c2a4f6f6c17fdecb7bc68b86db6099f5d6ffdc09b8b8732e 0.600000000000 1426666 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": 966905, "vin": [ { "gen": { "height": 966895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9efb7cd78a2d1d40c2a4f6f6c17fdecb7bc68b86db6099f5d6ffdc09b8b8732e" } } ], "extra": [ 1, 94, 99, 83, 158, 134, 164, 219, 128, 246, 235, 166, 130, 13, 145, 153, 81, 0, 194, 68, 71, 211, 110, 51, 82, 69, 215, 79, 108, 230, 43, 97, 231, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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