Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd78f188110ebe089c44b1af74bb4d9a04773052b384b386d182cdd54ecb1b14

Tx prefix hash: 822bddf9d470f8b69a389a2151fe4caf51f639582fbd4c2c93436d501068729a
Tx public key: 4ff19568c8c3cbc15a99335e1094180bf79b36e9c648caf71843874cfec753f0
Timestamp: 1577027008 Timestamp [UCT]: 2019-12-22 15:03:28 Age [y:d:h:m:s]: 05:117:14:27:00
Block: 29663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1233542 RingCT/type: yes/0
Extra: 014ff19568c8c3cbc15a99335e1094180bf79b36e9c648caf71843874cfec753f002110000002d8a2ee0d9000000000000000000

1 output(s) for total of 489.457547847000 dcy

stealth address amount amount idx
00: ac8e044fa8a2c14e19bfc55a3f5f79fc1e201667ef12fa6f6f2725bbefbb37af 489.457547847000 48815 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": 29673, "vin": [ { "gen": { "height": 29663 } } ], "vout": [ { "amount": 489457547847, "target": { "key": "ac8e044fa8a2c14e19bfc55a3f5f79fc1e201667ef12fa6f6f2725bbefbb37af" } } ], "extra": [ 1, 79, 241, 149, 104, 200, 195, 203, 193, 90, 153, 51, 94, 16, 148, 24, 11, 247, 155, 54, 233, 198, 72, 202, 247, 24, 67, 135, 76, 254, 199, 83, 240, 2, 17, 0, 0, 0, 45, 138, 46, 224, 217, 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