Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 772d384a9375b8fcf77ea8e0647f909a51746b6c0443fd0f24e5460e27eb1ee1

Tx prefix hash: 09ab4a2f06717d5a6c7cf92b7c6f80e414f5b168e9e342313571b9e4177b4655
Tx public key: 235224355fd95bbd3cef6dbf1aa029c210e5712dd4078dcb28178d3da1937c41
Timestamp: 1724363478 Timestamp [UCT]: 2024-08-22 21:51:18 Age [y:d:h:m:s]: 01:078:17:43:26
Block: 1093744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314706 RingCT/type: yes/0
Extra: 01235224355fd95bbd3cef6dbf1aa029c210e5712dd4078dcb28178d3da1937c41021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ee7313fa0e917289c2be93a1175626ebf736e0689289a900f65a0471231eba9 0.600000000000 1568749 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": 1093754, "vin": [ { "gen": { "height": 1093744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ee7313fa0e917289c2be93a1175626ebf736e0689289a900f65a0471231eba9" } } ], "extra": [ 1, 35, 82, 36, 53, 95, 217, 91, 189, 60, 239, 109, 191, 26, 160, 41, 194, 16, 229, 113, 45, 212, 7, 141, 203, 40, 23, 141, 61, 161, 147, 124, 65, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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