Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 085f8871de545df305409d5cb7518d85d2775ba39ee86d29e75c53d19e857fb5

Tx prefix hash: dfec750927056eb82819bfb8c7f41326a23f4dfdfc854a4e4502683d580726d9
Tx public key: 1a725976d54d5ee15ddbb2093dbb9d893fc5e7b57205f5cd4930e3663d7284f4
Timestamp: 1714497052 Timestamp [UCT]: 2024-04-30 17:10:52 Age [y:d:h:m:s]: 00:340:08:13:05
Block: 1011934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243284 RingCT/type: yes/0
Extra: 011a725976d54d5ee15ddbb2093dbb9d893fc5e7b57205f5cd4930e3663d7284f402110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b2bc3aeb9974ba439bb1ee1c0b028ae2b4816755d607393b05fcc4b53a6fce4 0.600000000000 1474300 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": 1011944, "vin": [ { "gen": { "height": 1011934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b2bc3aeb9974ba439bb1ee1c0b028ae2b4816755d607393b05fcc4b53a6fce4" } } ], "extra": [ 1, 26, 114, 89, 118, 213, 77, 94, 225, 93, 219, 178, 9, 61, 187, 157, 137, 63, 197, 231, 181, 114, 5, 245, 205, 73, 48, 227, 102, 61, 114, 132, 244, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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