Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 890f35416c7ca686aeab77e72a7be2902d5ab2426469be4136e9177ea056f57c

Tx prefix hash: 7b50bb6592bdc98985bc3acaedfa431ca6df058b33c40d48b00de1d71a20ab03
Tx public key: 344851d229b87cfeed02609e3a4db59781b8ad3aa4f27884e64b64cb0a7edc3d
Timestamp: 1648899053 Timestamp [UCT]: 2022-04-02 11:30:53 Age [y:d:h:m:s]: 02:239:00:08:46
Block: 471604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 690485 RingCT/type: yes/0
Extra: 01344851d229b87cfeed02609e3a4db59781b8ad3aa4f27884e64b64cb0a7edc3d02110000001a2e6b1fd5000000000000000000

1 output(s) for total of 16.803142213000 dcy

stealth address amount amount idx
00: 9c27cd956125a740b3ef65d3b34b8597173f8e82fac8a8e0764a161af2192001 16.803142213000 890966 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": 471614, "vin": [ { "gen": { "height": 471604 } } ], "vout": [ { "amount": 16803142213, "target": { "key": "9c27cd956125a740b3ef65d3b34b8597173f8e82fac8a8e0764a161af2192001" } } ], "extra": [ 1, 52, 72, 81, 210, 41, 184, 124, 254, 237, 2, 96, 158, 58, 77, 181, 151, 129, 184, 173, 58, 164, 242, 120, 132, 230, 75, 100, 203, 10, 126, 220, 61, 2, 17, 0, 0, 0, 26, 46, 107, 31, 213, 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