Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 534063f58100d89608368daf31ef4123f913e8a7aa22105d0c83d9977f019f93

Tx prefix hash: 1f620776b57ccbbeeba6b35b0dc5d55eb52c4e7f928abf00c58a30bb4dba9a16
Tx public key: 03322c83bdc5c74d7c2378048592fffa07dc77299dc713856f641f96a8066dc6
Timestamp: 1707210250 Timestamp [UCT]: 2024-02-06 09:04:10 Age [y:d:h:m:s]: 01:072:05:27:11
Block: 951511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312694 RingCT/type: yes/0
Extra: 0103322c83bdc5c74d7c2378048592fffa07dc77299dc713856f641f96a8066dc60211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b563e3a8a63c2770b9c3df17a70c0fd60b6cccea67305b50ab6cea2185d638a8 0.600000000000 1410283 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": 951521, "vin": [ { "gen": { "height": 951511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b563e3a8a63c2770b9c3df17a70c0fd60b6cccea67305b50ab6cea2185d638a8" } } ], "extra": [ 1, 3, 50, 44, 131, 189, 197, 199, 77, 124, 35, 120, 4, 133, 146, 255, 250, 7, 220, 119, 41, 157, 199, 19, 133, 111, 100, 31, 150, 168, 6, 109, 198, 2, 17, 0, 0, 0, 8, 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