Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 764f5f63812d0b7b3c1f59b66dcb19e82ea38cd05e0ffadee85350e7e69e2ca1

Tx prefix hash: a3c9c169059cef00fd02d5123d899d872689f6badd16aadde0df0f82bfefdbb3
Tx public key: be055b910df4da4d378ce93f0b679781178965aad1254b416ffba1b7569100fa
Timestamp: 1633586007 Timestamp [UCT]: 2021-10-07 05:53:27 Age [y:d:h:m:s]: 03:197:03:07:21
Block: 348305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 917864 RingCT/type: yes/0
Extra: 01be055b910df4da4d378ce93f0b679781178965aad1254b416ffba1b7569100fa0211000000075410958b000000000000000000

1 output(s) for total of 43.044867185000 dcy

stealth address amount amount idx
00: 5269e1e22592ebf1e11d9f35abf89cb777299e2f970a7df412f73a077c02ffb6 43.044867185000 713339 of 0

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": 348315, "vin": [ { "gen": { "height": 348305 } } ], "vout": [ { "amount": 43044867185, "target": { "key": "5269e1e22592ebf1e11d9f35abf89cb777299e2f970a7df412f73a077c02ffb6" } } ], "extra": [ 1, 190, 5, 91, 145, 13, 244, 218, 77, 55, 140, 233, 63, 11, 103, 151, 129, 23, 137, 101, 170, 209, 37, 75, 65, 111, 251, 161, 183, 86, 145, 0, 250, 2, 17, 0, 0, 0, 7, 84, 16, 149, 139, 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