Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 233650b51a21a53243061c9f558740c4b7a0738dbd605b92e7e72358138c2d65

Tx prefix hash: a108606c8f0cfc78464c04186954c1ff0802ed6f9accebb4d3dc54240a57b7d6
Tx public key: 04ec872133f1da50666c2095f41a0b20feb9c7cb911d3b7515eca7cf69296579
Timestamp: 1580832507 Timestamp [UCT]: 2020-02-04 16:08:27 Age [y:d:h:m:s]: 04:347:09:35:16
Block: 58636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1139640 RingCT/type: yes/0
Extra: 0104ec872133f1da50666c2095f41a0b20feb9c7cb911d3b7515eca7cf692965790211000000154943cd9f000000000000000000

1 output(s) for total of 392.387723563000 dcy

stealth address amount amount idx
00: d9ee847091357d0f5d97c075e6dddca0a9e6b491ebca5e6eb65b066a82634c46 392.387723563000 108344 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": 58646, "vin": [ { "gen": { "height": 58636 } } ], "vout": [ { "amount": 392387723563, "target": { "key": "d9ee847091357d0f5d97c075e6dddca0a9e6b491ebca5e6eb65b066a82634c46" } } ], "extra": [ 1, 4, 236, 135, 33, 51, 241, 218, 80, 102, 108, 32, 149, 244, 26, 11, 32, 254, 185, 199, 203, 145, 29, 59, 117, 21, 236, 167, 207, 105, 41, 101, 121, 2, 17, 0, 0, 0, 21, 73, 67, 205, 159, 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