Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75818df91ad45ec159c35f1b6d63f640cf65c089d911eea2acf00b4a3f8e3096

Tx prefix hash: 030b4b3bd953567a9b3077828848edcd58b68a71a144a92e8f474307b32ec739
Tx public key: c3c9055d863a905facdbe185e19cc4133ad31f0b7828a10e9211961f318fd377
Timestamp: 1580567687 Timestamp [UCT]: 2020-02-01 14:34:47 Age [y:d:h:m:s]: 04:233:15:04:19
Block: 56521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1058217 RingCT/type: yes/0
Extra: 01c3c9055d863a905facdbe185e19cc4133ad31f0b7828a10e9211961f318fd377021100000002391a8d0e000000000000000000

1 output(s) for total of 398.790782946000 dcy

stealth address amount amount idx
00: 621de996e3fe26a240597f533de2ae55936ce52bf23e7a919052210a1c4bfb65 398.790782946000 104254 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": 56531, "vin": [ { "gen": { "height": 56521 } } ], "vout": [ { "amount": 398790782946, "target": { "key": "621de996e3fe26a240597f533de2ae55936ce52bf23e7a919052210a1c4bfb65" } } ], "extra": [ 1, 195, 201, 5, 93, 134, 58, 144, 95, 172, 219, 225, 133, 225, 156, 196, 19, 58, 211, 31, 11, 120, 40, 161, 14, 146, 17, 150, 31, 49, 143, 211, 119, 2, 17, 0, 0, 0, 2, 57, 26, 141, 14, 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