Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27696b3948fc5fc49bdcaa428ce75af7c9edd0105074900726e29dc9f189681d

Tx prefix hash: afbe8390d30d43d4346ebb462136e46f968d5bbb9dba4bdc662d12ad5bf56b93
Tx public key: 418f5ce8a5c36d8862094b92b8cbc8df301492f2cc7e461c67ea58dc4b18b433
Timestamp: 1675250726 Timestamp [UCT]: 2023-02-01 11:25:26 Age [y:d:h:m:s]: 02:120:06:13:51
Block: 687442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 607618 RingCT/type: yes/0
Extra: 01418f5ce8a5c36d8862094b92b8cbc8df301492f2cc7e461c67ea58dc4b18b433021100000006e6d27f9c000000000000000000

1 output(s) for total of 3.237570356000 dcy

stealth address amount amount idx
00: f603b8b6fa4014ecf9d4e1fe17d47bfaa9d6a372f71d92c53b67e01500d52aec 3.237570356000 1130004 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": 687452, "vin": [ { "gen": { "height": 687442 } } ], "vout": [ { "amount": 3237570356, "target": { "key": "f603b8b6fa4014ecf9d4e1fe17d47bfaa9d6a372f71d92c53b67e01500d52aec" } } ], "extra": [ 1, 65, 143, 92, 232, 165, 195, 109, 136, 98, 9, 75, 146, 184, 203, 200, 223, 48, 20, 146, 242, 204, 126, 70, 28, 103, 234, 88, 220, 75, 24, 180, 51, 2, 17, 0, 0, 0, 6, 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