Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80cc77e8a0414b1661eb4e28d630e0b26566ad06937a1efff61543037c8c01ed

Tx prefix hash: b58f2e887f2111ae11d453b7b6da7749d16f51099ca1e3744a1fd225bd326dcf
Tx public key: fe21b75031711e86953b72e6952f981eadfc43f657d6f3e6ae4c3c9b34d39741
Timestamp: 1706038156 Timestamp [UCT]: 2024-01-23 19:29:16 Age [y:d:h:m:s]: 01:103:23:55:28
Block: 941779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335439 RingCT/type: yes/0
Extra: 01fe21b75031711e86953b72e6952f981eadfc43f657d6f3e6ae4c3c9b34d3974102110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 272e9c811b7741941338e4cba53249706bf230ae40b5f98f5e2ec8802d3860f4 0.600000000000 1399935 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": 941789, "vin": [ { "gen": { "height": 941779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "272e9c811b7741941338e4cba53249706bf230ae40b5f98f5e2ec8802d3860f4" } } ], "extra": [ 1, 254, 33, 183, 80, 49, 113, 30, 134, 149, 59, 114, 230, 149, 47, 152, 30, 173, 252, 67, 246, 87, 214, 243, 230, 174, 76, 60, 155, 52, 211, 151, 65, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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