Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d109d7f6b1b97db09199da0208a517d5a64186c5e9a8bf5d502b28454f14b33b

Tx prefix hash: 0234f7e4bb7898ffe60a439df87e6d3feaf1463e7d45c1674eef1e80083a1f61
Tx public key: c13f13561cb526a3aa56346d77c71f1cef61f30bcf2319935a8b06ca16da915c
Timestamp: 1673196736 Timestamp [UCT]: 2023-01-08 16:52:16 Age [y:d:h:m:s]: 02:089:10:32:40
Block: 670389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 585598 RingCT/type: yes/0
Extra: 01c13f13561cb526a3aa56346d77c71f1cef61f30bcf2319935a8b06ca16da915c021100000005e6d27f9c000000000000000000

1 output(s) for total of 3.687422556000 dcy

stealth address amount amount idx
00: cee0e0266d458e304875dac8305ed5f787fb9e5e9e07c0b1e3036f28c89d59b1 3.687422556000 1111790 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": 670399, "vin": [ { "gen": { "height": 670389 } } ], "vout": [ { "amount": 3687422556, "target": { "key": "cee0e0266d458e304875dac8305ed5f787fb9e5e9e07c0b1e3036f28c89d59b1" } } ], "extra": [ 1, 193, 63, 19, 86, 28, 181, 38, 163, 170, 86, 52, 109, 119, 199, 31, 28, 239, 97, 243, 11, 207, 35, 25, 147, 90, 139, 6, 202, 22, 218, 145, 92, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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