Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79b6adbf13571c10dad45ddecb430a2921ad74c3b4245b49d374b3eb7e6eddaf

Tx prefix hash: 3f99f9e5ead885249c6dab9af016fb3b134f44b1f4ae174aae689d2839c03acf
Tx public key: 207704004f570130c1b7c6a97c329247470a5968ce5f3bef8930f2f19cef19b9
Timestamp: 1634535244 Timestamp [UCT]: 2021-10-18 05:34:04 Age [y:d:h:m:s]: 03:112:16:55:38
Block: 355387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 858276 RingCT/type: yes/0
Extra: 01207704004f570130c1b7c6a97c329247470a5968ce5f3bef8930f2f19cef19b902110000000bfdc024ec000000000000000000

1 output(s) for total of 40.780801448000 dcy

stealth address amount amount idx
00: e0fbd4c514e9fe8cb7df8ad87a0aafcd99f2058b95a6c9ddfad09c1ea5b66bdb 40.780801448000 725569 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": 355397, "vin": [ { "gen": { "height": 355387 } } ], "vout": [ { "amount": 40780801448, "target": { "key": "e0fbd4c514e9fe8cb7df8ad87a0aafcd99f2058b95a6c9ddfad09c1ea5b66bdb" } } ], "extra": [ 1, 32, 119, 4, 0, 79, 87, 1, 48, 193, 183, 198, 169, 124, 50, 146, 71, 71, 10, 89, 104, 206, 95, 59, 239, 137, 48, 242, 241, 156, 239, 25, 185, 2, 17, 0, 0, 0, 11, 253, 192, 36, 236, 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