Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14b3d47fbf43931695a31fc5dcafee7417e3dc24a7778eb75b52caacacf62f49

Tx prefix hash: 4d09eeddc3289c08f9514dea8c1d110b5b3dfb8a7474b6a6ed3eae8295b0ec00
Tx public key: ccd45ce62728b90cc1392328d41a27f34ef01930ef00b7e00b11ad8c59ab2a5d
Timestamp: 1705575797 Timestamp [UCT]: 2024-01-18 11:03:17 Age [y:d:h:m:s]: 01:070:22:17:19
Block: 937956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311784 RingCT/type: yes/0
Extra: 01ccd45ce62728b90cc1392328d41a27f34ef01930ef00b7e00b11ad8c59ab2a5d02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e64b3a9928e59f6cb64ed628ea9148eef40831424fedaa77e3bca8f55e741f9c 0.600000000000 1396020 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": 937966, "vin": [ { "gen": { "height": 937956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e64b3a9928e59f6cb64ed628ea9148eef40831424fedaa77e3bca8f55e741f9c" } } ], "extra": [ 1, 204, 212, 92, 230, 39, 40, 185, 12, 193, 57, 35, 40, 212, 26, 39, 243, 78, 240, 25, 48, 239, 0, 183, 224, 11, 17, 173, 140, 89, 171, 42, 93, 2, 17, 0, 0, 0, 5, 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