Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06be19339feeb7c95977199202b4160c6de423aa947101596257db12d4c86fea

Tx prefix hash: 04c0da48b630d1403c09e8a553e0c636f205079e8ce51c856586063490111dc8
Tx public key: cff2f0ef49bd5f1e24e83463fa8b7fd1baa9db047f1e1605f318ba92d1c44c14
Timestamp: 1641062553 Timestamp [UCT]: 2022-01-01 18:42:33 Age [y:d:h:m:s]: 03:037:21:40:51
Block: 408338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 805857 RingCT/type: yes/0
Extra: 01cff2f0ef49bd5f1e24e83463fa8b7fd1baa9db047f1e1605f318ba92d1c44c14021100000001edb0d4a3000000000000000000

1 output(s) for total of 27.227454191000 dcy

stealth address amount amount idx
00: e9ff19ea82280193b042edd12e719b97c6ad41e6d7e0af2f1b0d96b0d4d343b3 27.227454191000 810327 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": 408348, "vin": [ { "gen": { "height": 408338 } } ], "vout": [ { "amount": 27227454191, "target": { "key": "e9ff19ea82280193b042edd12e719b97c6ad41e6d7e0af2f1b0d96b0d4d343b3" } } ], "extra": [ 1, 207, 242, 240, 239, 73, 189, 95, 30, 36, 232, 52, 99, 250, 139, 127, 209, 186, 169, 219, 4, 127, 30, 22, 5, 243, 24, 186, 146, 209, 196, 76, 20, 2, 17, 0, 0, 0, 1, 237, 176, 212, 163, 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