Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fe50b7c7c072a3970da0708b3073d46cdfcdf0807d829509a2e60299210172b

Tx prefix hash: be955b832b295c65adf71ddee0b32e33f4aba97d741528d27b7688acaf1be7dc
Tx public key: 26fb81ab691525d70a7b711e518bc532cf846d7efb380a0422823d99e9e15bae
Timestamp: 1702513027 Timestamp [UCT]: 2023-12-14 00:17:07 Age [y:d:h:m:s]: 01:126:05:47:05
Block: 912577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351375 RingCT/type: yes/0
Extra: 0126fb81ab691525d70a7b711e518bc532cf846d7efb380a0422823d99e9e15bae02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b38787561e2e81e1fda0b792f5a81d5252e0187d8c5398fb9806293e63e2097d 0.600000000000 1369805 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": 912587, "vin": [ { "gen": { "height": 912577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b38787561e2e81e1fda0b792f5a81d5252e0187d8c5398fb9806293e63e2097d" } } ], "extra": [ 1, 38, 251, 129, 171, 105, 21, 37, 215, 10, 123, 113, 30, 81, 139, 197, 50, 207, 132, 109, 126, 251, 56, 10, 4, 34, 130, 61, 153, 233, 225, 91, 174, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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