Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a4f706ea1e7f11b7f08d1b51da69a008a46129b4ab747ec33007a4153ee3ab8

Tx prefix hash: ca6aca71784f08a8083dc86e64fee7f361e1060b547f208568869876035c1aa3
Tx public key: 1583b41df47141c856c3c835281f9278eb7b97ead1cbc4193a20f3a8e8be3e03
Timestamp: 1580975306 Timestamp [UCT]: 2020-02-06 07:48:26 Age [y:d:h:m:s]: 04:288:17:12:30
Block: 59566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1097922 RingCT/type: yes/0
Extra: 011583b41df47141c856c3c835281f9278eb7b97ead1cbc4193a20f3a8e8be3e03021100000006026b59f3000000000000000000

1 output(s) for total of 389.613443744000 dcy

stealth address amount amount idx
00: fb287f8c7913929c3b6d59d6f43f03a5a8f35a8185490df5cea3b412a1f50cf5 389.613443744000 109990 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": 59576, "vin": [ { "gen": { "height": 59566 } } ], "vout": [ { "amount": 389613443744, "target": { "key": "fb287f8c7913929c3b6d59d6f43f03a5a8f35a8185490df5cea3b412a1f50cf5" } } ], "extra": [ 1, 21, 131, 180, 29, 244, 113, 65, 200, 86, 195, 200, 53, 40, 31, 146, 120, 235, 123, 151, 234, 209, 203, 196, 25, 58, 32, 243, 168, 232, 190, 62, 3, 2, 17, 0, 0, 0, 6, 2, 107, 89, 243, 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