Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 133e9fc96c26df398347a598ff31d20c702bc7990de378815a27a36e89869c1d

Tx prefix hash: 2a7bdbe2934b95ae0ba1f46479531e5feea2ea6fd6067ecfd68f74710b130825
Tx public key: df5e523d170d6958759f4d7ead63f5bfe2549048b806f633b050717d270144d7
Timestamp: 1739571975 Timestamp [UCT]: 2025-02-14 22:26:15 Age [y:d:h:m:s]: 00:327:21:24:54
Block: 1219382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232175 RingCT/type: yes/0
Extra: 01df5e523d170d6958759f4d7ead63f5bfe2549048b806f633b050717d270144d70211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa35d20c77244e7e25cf1fb9c06b0c535f51c4a1d2d95b6c9b461a5f3acb900d 0.600000000000 1706207 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": 1219392, "vin": [ { "gen": { "height": 1219382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa35d20c77244e7e25cf1fb9c06b0c535f51c4a1d2d95b6c9b461a5f3acb900d" } } ], "extra": [ 1, 223, 94, 82, 61, 23, 13, 105, 88, 117, 159, 77, 126, 173, 99, 245, 191, 226, 84, 144, 72, 184, 6, 246, 51, 176, 80, 113, 125, 39, 1, 68, 215, 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