Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c26a5fbd58532dd52cf37adf0155520fcc91ca41056e606779568b82599d0b36

Tx prefix hash: 04ecf25c4987f61712e0cb9023f200b4fc30cfd802bc7e3dbf5fd50b3a93d7a7
Tx public key: 1de52e03be822ed5d960220276c29592a2626fff2b70a9a606d2f714e53abaa9
Timestamp: 1718946709 Timestamp [UCT]: 2024-06-21 05:11:49 Age [y:d:h:m:s]: 00:293:20:42:11
Block: 1048835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209980 RingCT/type: yes/0
Extra: 011de52e03be822ed5d960220276c29592a2626fff2b70a9a606d2f714e53abaa90211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6435ea1a2ce63a4a24abb2084f6ee0c19b5f77680c1744e7ac4ee6906900c5b8 0.600000000000 1518922 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": 1048845, "vin": [ { "gen": { "height": 1048835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6435ea1a2ce63a4a24abb2084f6ee0c19b5f77680c1744e7ac4ee6906900c5b8" } } ], "extra": [ 1, 29, 229, 46, 3, 190, 130, 46, 213, 217, 96, 34, 2, 118, 194, 149, 146, 162, 98, 111, 255, 43, 112, 169, 166, 6, 210, 247, 20, 229, 58, 186, 169, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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