Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf988c2bf19dbde071ea751005410277ef81190a01b140c0b7e40d432f719184

Tx prefix hash: 9227711e65093bf4a2c014b856384cda95aaf97f29ff63671e8a98eb7cba524e
Tx public key: 11de83bb4a2c2cd6ebafd966a7dc337f3ee21028ecc95244e5a2657f52e7cc88
Timestamp: 1609555999 Timestamp [UCT]: 2021-01-02 02:53:19 Age [y:d:h:m:s]: 03:332:03:59:59
Block: 173434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 990670 RingCT/type: yes/0
Extra: 0111de83bb4a2c2cd6ebafd966a7dc337f3ee21028ecc95244e5a2657f52e7cc88021100000025aad74b3a000000000000000000

1 output(s) for total of 163.433779028000 dcy

stealth address amount amount idx
00: 0c38083d89a78c43a0d79eac852a7003aab1fe2399a27a0fe7bc73a31b13a0f4 163.433779028000 329041 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": 173444, "vin": [ { "gen": { "height": 173434 } } ], "vout": [ { "amount": 163433779028, "target": { "key": "0c38083d89a78c43a0d79eac852a7003aab1fe2399a27a0fe7bc73a31b13a0f4" } } ], "extra": [ 1, 17, 222, 131, 187, 74, 44, 44, 214, 235, 175, 217, 102, 167, 220, 51, 127, 62, 226, 16, 40, 236, 201, 82, 68, 229, 162, 101, 127, 82, 231, 204, 136, 2, 17, 0, 0, 0, 37, 170, 215, 75, 58, 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