Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4fac3de99291104d1dc4abba08751200bcd39dca55cd7867b0f1e2a3b668656

Tx prefix hash: 86f86caaaff27a06de6830c68b2782f53419e71d30d971bb01f53d43e67d2b51
Tx public key: 6d770714358d37281562ae320297cfc1e61416d078824e03861b70c406bb50c6
Timestamp: 1694559916 Timestamp [UCT]: 2023-09-12 23:05:16 Age [y:d:h:m:s]: 01:128:00:35:47
Block: 846828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352820 RingCT/type: yes/0
Extra: 016d770714358d37281562ae320297cfc1e61416d078824e03861b70c406bb50c60211000000034b8f5122000000000000000000

1 output(s) for total of 0.959637835000 dcy

stealth address amount amount idx
00: 0016e8c9e60bb0bff34e55c2fbafb307d7f5239a0de2d3f3c0e378ce5ec19810 0.959637835000 1300316 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": 846838, "vin": [ { "gen": { "height": 846828 } } ], "vout": [ { "amount": 959637835, "target": { "key": "0016e8c9e60bb0bff34e55c2fbafb307d7f5239a0de2d3f3c0e378ce5ec19810" } } ], "extra": [ 1, 109, 119, 7, 20, 53, 141, 55, 40, 21, 98, 174, 50, 2, 151, 207, 193, 230, 20, 22, 208, 120, 130, 78, 3, 134, 27, 112, 196, 6, 187, 80, 198, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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