Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e5995d5a7822a408d464769cddfc80bf4f64ef0f8a6856a03eb7223f4066768

Tx prefix hash: a5dd52bb7f90e08cd0715735748e15d6b97e663829df895d56edd1a8cf145656
Tx public key: 8f4df1d2072903aca1d1633962af41baf7a48224be88d86acced063fa2b369c9
Timestamp: 1583531779 Timestamp [UCT]: 2020-03-06 21:56:19 Age [y:d:h:m:s]: 04:296:15:26:18
Block: 77690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106627 RingCT/type: yes/0
Extra: 018f4df1d2072903aca1d1633962af41baf7a48224be88d86acced063fa2b369c902110000000ae89b4e54000000000000000000

1 output(s) for total of 339.298213273000 dcy

stealth address amount amount idx
00: bd100eb83d650b12aa1e8248540b7e0f36ad51fa4b7874726d7a11a8f68c8479 339.298213273000 142853 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": 77700, "vin": [ { "gen": { "height": 77690 } } ], "vout": [ { "amount": 339298213273, "target": { "key": "bd100eb83d650b12aa1e8248540b7e0f36ad51fa4b7874726d7a11a8f68c8479" } } ], "extra": [ 1, 143, 77, 241, 210, 7, 41, 3, 172, 161, 209, 99, 57, 98, 175, 65, 186, 247, 164, 130, 36, 190, 136, 216, 106, 204, 237, 6, 63, 162, 179, 105, 201, 2, 17, 0, 0, 0, 10, 232, 155, 78, 84, 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