Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 523f60af0285c2954d9859c9f48b17358c0b84e8a402abc6d8cee52968f84ea8

Tx prefix hash: 8e168f696c91c5c42a0bc6544e0a5ea60d7b9ac5d2bbf4a9f4f1eb77131e1c2c
Tx public key: 37694ad7e82852b55e14582d3db20c36594fece20dc449869aba74bf1094c3fc
Timestamp: 1581946223 Timestamp [UCT]: 2020-02-17 13:30:23 Age [y:d:h:m:s]: 05:026:17:46:52
Block: 66647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1172313 RingCT/type: yes/0
Extra: 0137694ad7e82852b55e14582d3db20c36594fece20dc449869aba74bf1094c3fc0211000000020aca7173000000000000000000

1 output(s) for total of 369.123445573000 dcy

stealth address amount amount idx
00: 34b4856e03944cf4928e8155389c27a9adf8fc0d4f8cbbd4927d13c8d2a0bd21 369.123445573000 122794 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": 66657, "vin": [ { "gen": { "height": 66647 } } ], "vout": [ { "amount": 369123445573, "target": { "key": "34b4856e03944cf4928e8155389c27a9adf8fc0d4f8cbbd4927d13c8d2a0bd21" } } ], "extra": [ 1, 55, 105, 74, 215, 232, 40, 82, 181, 94, 20, 88, 45, 61, 178, 12, 54, 89, 79, 236, 226, 13, 196, 73, 134, 154, 186, 116, 191, 16, 148, 195, 252, 2, 17, 0, 0, 0, 2, 10, 202, 113, 115, 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