Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc8c1b25fca4c074cc5a7e69ef953bab6dd9f02bc59f85ca3bf8cfe7a12649c1

Tx prefix hash: 27b56da2767111dcf259df6131c0780d0a3066b2957203b2d3db65bcb79ecdf8
Tx public key: 747f3424853fcd50a25863e334ad334a1db537a0d477c140fb75f715872d9f46
Timestamp: 1699623312 Timestamp [UCT]: 2023-11-10 13:35:12 Age [y:d:h:m:s]: 01:140:04:48:22
Block: 888628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361384 RingCT/type: yes/0
Extra: 01747f3424853fcd50a25863e334ad334a1db537a0d477c140fb75f715872d9f46021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.697600124000 dcy

stealth address amount amount idx
00: 8f767a20209f8f1c4810e661e01af6ac854d60a4b5d3101b141dbb33ca13f7c7 0.697600124000 1344581 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": 888638, "vin": [ { "gen": { "height": 888628 } } ], "vout": [ { "amount": 697600124, "target": { "key": "8f767a20209f8f1c4810e661e01af6ac854d60a4b5d3101b141dbb33ca13f7c7" } } ], "extra": [ 1, 116, 127, 52, 36, 133, 63, 205, 80, 162, 88, 99, 227, 52, 173, 51, 74, 29, 181, 55, 160, 212, 119, 193, 64, 251, 117, 247, 21, 135, 45, 159, 70, 2, 17, 0, 0, 0, 1, 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