Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3337f4423b7030ae7a90396ef18e228d5c74034cf80b4af4dc3f7d2cd4490617

Tx prefix hash: b00d14ae90e25094537b6b3c45913cdd75233d5c2e3b97f822b25133ea01f7d6
Tx public key: fc59504491a5801a7a53a4f0591c1faae6d43f55cadfb99b9cee524ab21d7555
Timestamp: 1718209056 Timestamp [UCT]: 2024-06-12 16:17:36 Age [y:d:h:m:s]: 00:354:04:50:30
Block: 1042707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253169 RingCT/type: yes/0
Extra: 01fc59504491a5801a7a53a4f0591c1faae6d43f55cadfb99b9cee524ab21d75550211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0df9dcc6892ff046ccc21e5fb39443991d768cd038bb613a98d76587bba55ec8 0.600000000000 1511690 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": 1042717, "vin": [ { "gen": { "height": 1042707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0df9dcc6892ff046ccc21e5fb39443991d768cd038bb613a98d76587bba55ec8" } } ], "extra": [ 1, 252, 89, 80, 68, 145, 165, 128, 26, 122, 83, 164, 240, 89, 28, 31, 170, 230, 212, 63, 85, 202, 223, 185, 155, 156, 238, 82, 74, 178, 29, 117, 85, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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