Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21e0ad01038962255742e419454547dd642db11925dd7fb2c8e0eebf4673b193

Tx prefix hash: 94d87959a9fdd693d0f7fdf55ddb2b705b0edb5ce5b28c008736c2d068350b34
Tx public key: 8152314ed06b94b4c5479b3b541da5fde720c0b4e01681498c30d70fdb3d7b40
Timestamp: 1709399055 Timestamp [UCT]: 2024-03-02 17:04:15 Age [y:d:h:m:s]: 00:330:04:02:01
Block: 969677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236231 RingCT/type: yes/0
Extra: 018152314ed06b94b4c5479b3b541da5fde720c0b4e01681498c30d70fdb3d7b4002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aea8780f60d0065a1e85a677b535854cbba5e87b36735f8724dce77df70a763e 0.600000000000 1429514 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": 969687, "vin": [ { "gen": { "height": 969677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aea8780f60d0065a1e85a677b535854cbba5e87b36735f8724dce77df70a763e" } } ], "extra": [ 1, 129, 82, 49, 78, 208, 107, 148, 180, 197, 71, 155, 59, 84, 29, 165, 253, 231, 32, 192, 180, 224, 22, 129, 73, 140, 48, 215, 15, 219, 61, 123, 64, 2, 17, 0, 0, 0, 1, 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