Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae6951900105903ddf51cca1b3bbe26cb5d1c2017952d6b50e97db8b7e0be6e4

Tx prefix hash: a29c9e383a91388fd964243c5acf959d00b81f84f2d7a5e48ac2423aa862fa90
Tx public key: 791dc228188a197056feea72aedaf5b4aece9ff5ead2b2e817948c48b7474eed
Timestamp: 1634028638 Timestamp [UCT]: 2021-10-12 08:50:38 Age [y:d:h:m:s]: 03:196:22:52:00
Block: 351559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 918161 RingCT/type: yes/0
Extra: 01791dc228188a197056feea72aedaf5b4aece9ff5ead2b2e817948c48b7474eed02110000000ffdc024ec000000000000000000

1 output(s) for total of 41.990115078000 dcy

stealth address amount amount idx
00: 80588a9b3c12219ecbfb6345ec6a527043c9b8aa1ed35d1d1190022f1b762115 41.990115078000 718895 of 0

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": 351569, "vin": [ { "gen": { "height": 351559 } } ], "vout": [ { "amount": 41990115078, "target": { "key": "80588a9b3c12219ecbfb6345ec6a527043c9b8aa1ed35d1d1190022f1b762115" } } ], "extra": [ 1, 121, 29, 194, 40, 24, 138, 25, 112, 86, 254, 234, 114, 174, 218, 245, 180, 174, 206, 159, 245, 234, 210, 178, 232, 23, 148, 140, 72, 183, 71, 78, 237, 2, 17, 0, 0, 0, 15, 253, 192, 36, 236, 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