Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2052da5d223e6b62a0c4ff2fcfa15ae055d81afb466a52b93ba71e03f3bcd7af

Tx prefix hash: 3a68bcc66b1e7ca9b922cb84bcb9d220f743a18c517e59847253fe85bb0a80bf
Tx public key: fa71605bd49765c386cf9677d5d30cbe3aa1a432b05e81ed79eb93ddb3258159
Timestamp: 1578752615 Timestamp [UCT]: 2020-01-11 14:23:35 Age [y:d:h:m:s]: 05:021:03:51:30
Block: 43280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1165246 RingCT/type: yes/0
Extra: 01fa71605bd49765c386cf9677d5d30cbe3aa1a432b05e81ed79eb93ddb325815902110000000a4943cd9f000000000000000000

1 output(s) for total of 441.160110109000 dcy

stealth address amount amount idx
00: 3e46e1356b5ebc4562cba2fccc1695e18e5878bc1d8f2f582437491c2954a41a 441.160110109000 78313 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": 43290, "vin": [ { "gen": { "height": 43280 } } ], "vout": [ { "amount": 441160110109, "target": { "key": "3e46e1356b5ebc4562cba2fccc1695e18e5878bc1d8f2f582437491c2954a41a" } } ], "extra": [ 1, 250, 113, 96, 91, 212, 151, 101, 195, 134, 207, 150, 119, 213, 211, 12, 190, 58, 161, 164, 50, 176, 94, 129, 237, 121, 235, 147, 221, 179, 37, 129, 89, 2, 17, 0, 0, 0, 10, 73, 67, 205, 159, 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