Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f5ea10628d5cd9fb872515a84695262c541d8021ef3869cbfc13615ad3765cd

Tx prefix hash: 865eea0379920fd48661cd95fda65678406f7d935e6d4b244e91c53038119d72
Tx public key: 67c98b59aa95cb512a345b92872672edd3a87d98990418b5b914a1ad0e31817e
Timestamp: 1679423292 Timestamp [UCT]: 2023-03-21 18:28:12 Age [y:d:h:m:s]: 02:021:09:17:34
Block: 722055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 536818 RingCT/type: yes/0
Extra: 0167c98b59aa95cb512a345b92872672edd3a87d98990418b5b914a1ad0e31817e02110000000175e3f0e9000000000000000000

1 output(s) for total of 2.486176326000 dcy

stealth address amount amount idx
00: 35af13bacc02be540f688d00f712a6a0b0b84f9945273b7ab9b7453264779dd6 2.486176326000 1166962 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": 722065, "vin": [ { "gen": { "height": 722055 } } ], "vout": [ { "amount": 2486176326, "target": { "key": "35af13bacc02be540f688d00f712a6a0b0b84f9945273b7ab9b7453264779dd6" } } ], "extra": [ 1, 103, 201, 139, 89, 170, 149, 203, 81, 42, 52, 91, 146, 135, 38, 114, 237, 211, 168, 125, 152, 153, 4, 24, 181, 185, 20, 161, 173, 14, 49, 129, 126, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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