Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e2d4787614cff5bfbf82909138083c19d2d9c30ed750bd7562d55933afabafc

Tx prefix hash: 4f10e7a06887d63975d6c879084183b81c852769325afd29306139e1c4b3ed5e
Tx public key: 471fbf8a7d120e60ec7c9973c432c2ab8937b41799f563e146f20abb1d77afc0
Timestamp: 1710780264 Timestamp [UCT]: 2024-03-18 16:44:24 Age [y:d:h:m:s]: 01:081:02:32:28
Block: 981136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318979 RingCT/type: yes/0
Extra: 01471fbf8a7d120e60ec7c9973c432c2ab8937b41799f563e146f20abb1d77afc002110000000f59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e5f0a3eaa96cd355ea1ddead1be076d9b2d5c9172aa6c2bd676ada0dc8409f8 0.600000000000 1441229 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": 981146, "vin": [ { "gen": { "height": 981136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e5f0a3eaa96cd355ea1ddead1be076d9b2d5c9172aa6c2bd676ada0dc8409f8" } } ], "extra": [ 1, 71, 31, 191, 138, 125, 18, 14, 96, 236, 124, 153, 115, 196, 50, 194, 171, 137, 55, 180, 23, 153, 245, 99, 225, 70, 242, 10, 187, 29, 119, 175, 192, 2, 17, 0, 0, 0, 15, 89, 218, 211, 245, 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