Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f7711b6b6f4d1b241c0125a6407d642fdbf89a8cc0643214aa28ae6b9506701

Tx prefix hash: aa5d5a66dab85aeb3c03b1e1c003fa5f12a01c146ae7553f4ffdc0b1d152c98e
Tx public key: 54cc92f735f06bc3faefa708ea9fbf0126a713e577c64dc94332b14de42f6fad
Timestamp: 1699591488 Timestamp [UCT]: 2023-11-10 04:44:48 Age [y:d:h:m:s]: 01:364:10:55:30
Block: 888365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519375 RingCT/type: yes/0
Extra: 0154cc92f735f06bc3faefa708ea9fbf0126a713e577c64dc94332b14de42f6fad021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.699001291000 dcy

stealth address amount amount idx
00: e8a89cf59d25d07bf0c9f61f4d904caa73391d47fff722115817a1be58a7160d 0.699001291000 1344304 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": 888375, "vin": [ { "gen": { "height": 888365 } } ], "vout": [ { "amount": 699001291, "target": { "key": "e8a89cf59d25d07bf0c9f61f4d904caa73391d47fff722115817a1be58a7160d" } } ], "extra": [ 1, 84, 204, 146, 247, 53, 240, 107, 195, 250, 239, 167, 8, 234, 159, 191, 1, 38, 167, 19, 229, 119, 198, 77, 201, 67, 50, 177, 77, 228, 47, 111, 173, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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