Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 348586bfa3b19a7fe86c523a878accb4e524621224cdc025d928e64cf025f381

Tx prefix hash: 7ca85f451804f440f2b9335009cd90f265ec138d1cd1bc22213a9442b7d2714b
Tx public key: 7f9e72f82b1e64ca34228eba518cf0def2ef1c1d2f7554b242ebba980954b1ed
Timestamp: 1635586415 Timestamp [UCT]: 2021-10-30 09:33:35 Age [y:d:h:m:s]: 03:059:23:00:34
Block: 363547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 821345 RingCT/type: yes/0
Extra: 017f9e72f82b1e64ca34228eba518cf0def2ef1c1d2f7554b242ebba980954b1ed02110000000a328bb496000000000000000000

1 output(s) for total of 38.319362666000 dcy

stealth address amount amount idx
00: 1c80755df20e5647af8d0777af199a91b82dbb064edff01e4698137130f70aad 38.319362666000 738855 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": 363557, "vin": [ { "gen": { "height": 363547 } } ], "vout": [ { "amount": 38319362666, "target": { "key": "1c80755df20e5647af8d0777af199a91b82dbb064edff01e4698137130f70aad" } } ], "extra": [ 1, 127, 158, 114, 248, 43, 30, 100, 202, 52, 34, 142, 186, 81, 140, 240, 222, 242, 239, 28, 29, 47, 117, 84, 178, 66, 235, 186, 152, 9, 84, 177, 237, 2, 17, 0, 0, 0, 10, 50, 139, 180, 150, 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