Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3886a2b2d7a23b8c2d1f42e34d6c8f828c300247d4aa90c577cf3844ee931be

Tx prefix hash: 48101c83d816bcde5849ec88a87f850d267cb0ae940c4dd35f743f8be64c16a2
Tx public key: d4ec0f6ff71cb5a9fa91009359b291bae244ae7fdc37a742438577127599f757
Timestamp: 1735332677 Timestamp [UCT]: 2024-12-27 20:51:17 Age [y:d:h:m:s]: 00:093:13:50:53
Block: 1184539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66666 RingCT/type: yes/0
Extra: 01d4ec0f6ff71cb5a9fa91009359b291bae244ae7fdc37a742438577127599f7570211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffa371c0257aaa133a2de2437aac4b5fe4df1dee770ca2a8134ff39b25f8176b 0.600000000000 1670996 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": 1184549, "vin": [ { "gen": { "height": 1184539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffa371c0257aaa133a2de2437aac4b5fe4df1dee770ca2a8134ff39b25f8176b" } } ], "extra": [ 1, 212, 236, 15, 111, 247, 28, 181, 169, 250, 145, 0, 147, 89, 178, 145, 186, 226, 68, 174, 127, 220, 55, 167, 66, 67, 133, 119, 18, 117, 153, 247, 87, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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